INFO 4300 / CS4300 Information Retrieval slides adapted from - - PowerPoint PPT Presentation

INFO 4300 / CS4300 Information Retrieval slides adapted from Hinrich Sch¨ utze’s, linked from http://informationretrieval.org/

IR 11: Latent Semantic Indexing

Paul Ginsparg

Cornell University, Ithaca, NY

1 Oct 2009

1 / 44

Overview

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

2 / 44

Discussion 4, 6 Oct 2009

Read and be prepared to discuss the following paper: Scott Deerwester, Susan T. Dumais, George W. Furnas, Thomas

• K. Landauer, Richard Harshman, ”Indexing by latent semantic

analysis”. Journal of the American Society for Information Science, Volume 41, Issue 6, 1990. http://www3.interscience.wiley.com/cgi-bin/issuetoc?ID=10049584 Note that to access this paper from Wiley InterScience, you need to use a computer with a Cornell IP address. (also at /readings/jasis90f.pdf ) X = T0S0D′ ⇐ ⇒ C = UΣV T ˆ X = TSD′ ⇐ ⇒ Ck = UΣkV T

3 / 44

Outline

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

4 / 44

SVD

C an M × N matrix of rank r, C T its N × M transpose. CC T and C TC have the same r eigenvalues λ1, . . . , λr U = M × M matrix whose columns are the orthogonal eigenvectors of CC T V = N × N matrix whose columns are the orthogonal eigenvectors of C TC Then there’s a singular value decomposition (SVD) C = UΣV T where the M × N matrix Σ has Σii = σi for 1 ≤ i ≤ r, and zero otherwise. σi are called the singular values of C

5 / 44

Illustration of low rank approximation

Matrix entries affected by “zeroing out” smallest singular value indicated by dashed boxes Ck

= U Σk VT r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r r

6 / 44

LSI: Summary

We’ve decomposed the term-document matrix C into a product of three matrices. The term matrix U: consists of one (row) vector for each term The document matrix V T: consists of one (column) vector for each document The singular value matrix Σ: diagonal matrix with singular values, reflecting importance of each dimension Next: Why are we doing this?

7 / 44

Why the reduced matrix is “better”

C d1 d2 d3 d4 d5 d6 ship 1 1 boat 1

• cean

1 1 wood 1 1 1 tree 1 1 C2 d1 d2 d3 d4 d5 d6 ship 0.85 0.52 0.28 0.13 0.21 −0.08 boat 0.36 0.36 0.16 −0.20 −0.02 −0.18

• cean

1.01 0.72 0.36 −0.04 0.16 −0.21 wood 0.97 0.12 0.20 1.03 0.62 0.41 tree 0.12 −0.39 −0.08 0.90 0.41 0.49

Similarity of d2 and d3 in the

• riginal space: 0.

Similarity of d2 and d3 in the reduced space: 0.52 ∗ 0.28 + 0.36 ∗ 0.16 + 0.72 ∗ 0.36 + 0.12 ∗ 0.20 + −0.39 ∗ −0.08 ≈ 0.52 “boat” and “ship” are semantically similar. The “reduced” similarity measure reflects this. What property of the SVD reduction is responsible for improved similarity?

8 / 44

Documents in V T

2 space

9 / 44

Outline

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

10 / 44

Why we use LSI in information retrieval

LSI takes documents that are semantically similar (= talk about the same topics), . . . . . . but are not similar in the vector space (because they use different words) . . . . . . and re-represents them in a reduced vector space . . . . . . in which they have higher similarity. Thus, LSI addresses the problems of synonymy and semantic relatedness. Standard vector space: Synonyms contribute nothing to document similarity. Desired effect of LSI: Synonyms contribute strongly to document similarity.

11 / 44

How LSI addresses synonymy and semantic relatedness

The dimensionality reduction forces us to omit a lot of “detail”. We have to map differents words (= different dimensions of the full space) to the same dimension in the reduced space. The “cost” of mapping synonyms to the same dimension is much less than the cost of collapsing unrelated words. SVD selects the “least costly” mapping (see below). Thus, it will map synonyms to the same dimension. But it will avoid doing that for unrelated words. LSI like soft clustering: interprets each dimension of the reduced space as a cluster, and value of document on that dimension as its fractional membership in cluster

12 / 44

LSI: Comparison to other approaches

Recap: Relevance feedback and query expansion are used to increase recall in information retrieval – if query and documents have (in the extreme case) no terms in common. LSI increases recall and hurts precision. Thus, it addresses the same problems as (pseudo) relevance feedback and query expansion . . . . . . and it has the same problems.

13 / 44

Implementation

Compute SVD of term-document matrix Reduce the space and compute reduced document representations Map the query into the reduced space qk = qUΣ−1

k

This follows from: Ck = UΣkV T ⇒ C T

k = V ΣkUT ⇒ C TUΣ−1 k

= Vk (Note: intuitive to translate query into concept space using same transformation as used on documents: let jth column of V T represent the components of document j in concept space,

• ˆ

d(j) = Vji. Then d(j) = UkΣk ˆ d(j) and ˆ d(j) = Σ−1

k UT k

d(j). Same transformation on query vector q gives ˆ q = Σ−1

k UT k

q, and compare with other concept space vectors via cos( ˆ q, ˆ d(j)) ) Compute similarity of qk with all reduced documents in Vk. Output ranked list of documents as usual Exercise: What is the fundamental problem with this approach?

14 / 44

Optimality

SVD is optimal in the following sense. Keeping the k largest singular values and setting all others to zero gives you the optimal approximation of the original matrix C. Eckart-Young theorem Optimal: no other matrix of the same rank (= with the same underlying dimensionality) approximates C better. Measure of approximation is Frobenius norm: ||C||F =

• i
• j c2

ij

So LSI uses the “best possible” matrix. Caveat: There is only a tenuous relationship between the Frobenius norm and cosine similarity between documents.

15 / 44

Outline

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

16 / 44

Spelling correction

Two principal uses

Correcting documents being indexed Correcting user queries

Two different methods for spelling correction Isolated word spelling correction

Check each word on its own for misspelling Will not catch typos resulting in correctly spelled words, e.g., an asteroid that fell form the sky

Context-sensitive spelling correction

Look at surrounding words Can correct form/from error above

17 / 44

Correcting documents

We’re not interested in interactive spelling correction of documents (e.g., MS Word) in this class. In IR, we use document correction primarily for OCR’ed documents. The general philosophy in IR is: don’t change the documents.

18 / 44

Correcting queries

First: isolated word spelling correction Premise 1: There is a list of “correct words” from which the correct spellings come. Premise 2: We have a way of computing the distance between a misspelled word and a correct word. Simple spelling correction algorithm: return the “correct” word that has the smallest distance to the misspelled word. Example: informaton → information We can use the term vocabulary of the inverted index as the list of correct words. Why is this problematic?

19 / 44

Alternatives to using the term vocabulary

A standard dictionary (Webster’s, OED etc.) An industry-specific dictionary (for specialized IR systems) The term vocabulary of the collection, appropriately weighted

20 / 44

Distance between misspelled word and “correct” word

We will study several alternatives. Edit distance and Levenshtein distance Weighted edit distance k-gram overlap

21 / 44

Edit distance

The edit distance between string s1 and string s2 is the minimum number of basic operations that convert s1 to s2. Levenshtein distance: The admissible basic operations are insert, delete, and replace Levenshtein distance dog-do: 1 Levenshtein distance cat-cart: 1 Levenshtein distance cat-cut: 1 Levenshtein distance cat-act: 2 Damerau-Levenshtein distance cat-act: 1 Damerau-Levenshtein includes transposition as a fourth possible operation.

22 / 44

Levenshtein distance: Computation

f a s t 1 2 3 4 c 1 1 2 3 4 a 2 2 1 2 3 t 3 3 2 2 2 s 4 4 3 2 3

23 / 44

Levenshtein distance: Example

f a s t 1 1 2 2 3 3 4 4 c 1 1 1 2 2 1 2 3 2 2 3 4 3 3 4 5 4 4 a 2 2 2 2 3 2 1 3 3 1 3 4 2 2 4 5 3 3 t 3 3 3 3 4 3 3 2 4 2 2 3 3 2 2 4 3 2 s 4 4 4 4 5 4 4 3 5 3 2 3 4 2 3 3 3 3

24 / 44

Each cell of Levenshtein matrix

cost of getting here from my upper left neighbor (copy or replace) cost

• f

getting here from my upper neighbor (delete) cost of getting here from my left neighbor (insert) the minimum

• f

the three possible “move- ments”; the cheapest way of getting here

25 / 44

Levenshtein distance: algorithm

LevenshteinDistance(s1, s2) 1 for i ← 0 to |s1| 2 do m[i, 0] = i 3 for j ← 0 to |s2| 4 do m[0, j] = j 5 for i ← 1 to |s1| 6 do for j ← 1 to |s2| 7 do if s1[i] = s2[j] 8 then m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1]} 9 else m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1] + 1} 10 return m[|s1|, |s2|] Operations: insert, delete, replace, copy

26 / 44

Levenshtein distance: algorithm

LevenshteinDistance(s1, s2) 1 for i ← 0 to |s1| 2 do m[i, 0] = i 3 for j ← 0 to |s2| 4 do m[0, j] = j 5 for i ← 1 to |s1| 6 do for j ← 1 to |s2| 7 do if s1[i] = s2[j] 8 then m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1]} 9 else m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1] + 1} 10 return m[|s1|, |s2|] Operations: insert, delete, replace, copy

27 / 44

Levenshtein distance: algorithm

LevenshteinDistance(s1, s2) 1 for i ← 0 to |s1| 2 do m[i, 0] = i 3 for j ← 0 to |s2| 4 do m[0, j] = j 5 for i ← 1 to |s1| 6 do for j ← 1 to |s2| 7 do if s1[i] = s2[j] 8 then m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1]} 9 else m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1] + 1} 10 return m[|s1|, |s2|] Operations: insert, delete, replace, copy

28 / 44

Levenshtein distance: algorithm

LevenshteinDistance(s1, s2) 1 for i ← 0 to |s1| 2 do m[i, 0] = i 3 for j ← 0 to |s2| 4 do m[0, j] = j 5 for i ← 1 to |s1| 6 do for j ← 1 to |s2| 7 do if s1[i] = s2[j] 8 then m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1]} 9 else m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1] + 1} 10 return m[|s1|, |s2|] Operations: insert, delete, replace, copy

29 / 44

Levenshtein distance: algorithm

LevenshteinDistance(s1, s2) 1 for i ← 0 to |s1| 2 do m[i, 0] = i 3 for j ← 0 to |s2| 4 do m[0, j] = j 5 for i ← 1 to |s1| 6 do for j ← 1 to |s2| 7 do if s1[i] = s2[j] 8 then m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1]} 9 else m[i, j] = min{m[i − 1, j] + 1, m[i, j − 1] + 1, m[i − 1, j − 1] + 1} 10 return m[|s1|, |s2|] Operations: insert, delete, replace, copy

30 / 44

Weighted edit distance

As above, but weight of an operation depends on the characters involved. Meant to capture keyboard errors, e.g., m more likely to be mistyped as n than as q. Therefore, replacing m by n is a smaller edit distance than by q. We now require a weight matrix as input. Modify dynamic programming to handle weights.

31 / 44

Using edit distance for spelling correction

Given query, first enumerate all character sequences within a preset (possibly weighted) edit distance Intersect this set with our list of “correct” words Then suggest terms in the intersection to the user. Or do automatic correction – but this is potentially expensive and disempowers the user.

32 / 44

Example: Levenshtein distance oslo – snow

s n

• w

1 1 2 2 3 3 4 4

• 1

1 1 2 2 1 2 3 2 2 2 4 3 2 4 5 3 3 s 2 2 1 2 3 1 2 3 2 2 3 3 3 3 3 4 4 3 l 3 3 3 2 4 2 2 3 3 2 3 4 3 3 4 4 4 4

• 4

4 4 3 5 3 3 3 4 3 2 4 4 2 4 5 3 3 cost

• peration

input

• utput

1 delete

• *

(copy) s s 1 replace l n (copy)

• 1

insert * w

33 / 44

Outline

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

34 / 44

k-gram indexes for spelling correction

Enumerate all k-grams in the query term Use the k-gram index to retrieve “correct” words that match query term k-grams Threshold by number of matching k-grams E.g., only vocabulary terms that differ by at most 3 k-grams Example: bigram index, misspelled word bordroom Bigrams: bo, or, rd, dr, ro, oo, om

35 / 44

k-gram indexes for spelling correction: bordroom

rd aboard ardent

boardroom

border

• r

border lord morbid sordid bo aboard about

boardroom

border

✲ ✲ ✲ ✲ ✲ ✲ ✲ ✲ ✲ ✲ ✲ ✲

36 / 44

Context-sensitive spelling correction

Our example was: an asteroid that fell form the sky How can we correct form here? One idea: hit-based spelling correction

Retrieve “correct” terms close to each query term for flew form munich: flea for flew, from for form, munch for munich Now try all possible resulting phrases as queries with one word “fixed” at a time Try query “flea form munich” Try query “flew from munich” Try query “flew form munch” The correct query “flew from munich” has the most hits.

Suppose we have 7 alternatives for flew, 19 for form and 3 for munich, how many “corrected” phrases will we enumerate?

37 / 44

Context-sensitive spelling correction

The “hit-based” algorithm we just outlined is not very efficient. More efficient alternative: look at “collection” of queries, not documents

38 / 44

General issues in spelling correction

User interface

automatic vs. suggested correction Did you mean only works for one suggestion. What about multiple possible corrections? Tradeoff: simple vs. powerful UI

Cost

Spelling correction is potentially expensive. Avoid running on every query? Maybe just on queries that match few documents. Guess: Spelling correction of major search engines is efficient enough to be run on every query.

39 / 44

Peter Norvig’s spell corrector

http://norvig.com/spell-correct.html also http://www.facebook.com/video/video.php?v=644326502463

40 / 44

Outline

1

Recap

2

LSI in information retrieval

3

Edit distance

4

Spelling correction

5

Soundex

41 / 44

Soundex

Soundex is the basis for finding phonetic (as opposed to

• rthographic) alternatives.

Example: chebyshev / tchebyscheff Algorithm:

Turn every token to be indexed into a 4-character reduced form Do the same with query terms Build and search an index on the reduced forms

42 / 44

Soundex algorithm

1

Retain the first letter of the term.

2

Change all occurrences of the following letters to ’0’ (zero): ’A’, E’, ’I’, ’O’, ’U’, ’H’, ’W’, ’Y’

3

Change letters to digits as follows:

B, F, P, V to 1 C, G, J, K, Q, S, X, Z to 2 D,T to 3 L to 4 M, N to 5 R to 6

4

Repeatedly remove one out of each pair of consecutive identical digits

5

Remove all zeros from the resulting string; pad the resulting string with trailing zeros and return the first four positions, which will consist of a letter followed by three digits

43 / 44

Example: Soundex of HERMAN

Retain H ERMAN → 0RM0N 0RM0N → 06505 06505 → 06505 06505 → 655 Return H655 Will HERMANN generate the same code?

44 / 44

How useful is Soundex?

Not very – for information retrieval Ok for “high recall” tasks in other applications (e.g., Interpol) Zobel and Dart (1996) suggest better alternatives for phonetic matching in IR.

45 / 44