System and method for exploiting semantic annotations in executing keyword queries over a collection of text documents

[0001] The present invention generally relates to query systems and in particular, the present system relates to querying documents that are associated with semantic annotations. More specifically, the present system pertains to modeling such annotations as a type system and translating keyword queries into one or more complex queries against the this type system.

[0002] Conventional information retrieval systems (also known as text retrieval systems or text search engines) view document collections as standalone text corpora with little or no structured information associated with them. However, there are two primary reasons why such a view is no longer tenable. First, modern enterprise applications for customer relationship management, collaboration, technical support, etc., regularly create, manipulate, and process data that contains a mix of structured and unstructured information. In such applications, there is inherently a fair amount of structured information associated with every document. Second, advances in natural language processing techniques has led to the increased availability of powerful and accurate text analysis engines. These text analysis engines are capable of extracting structured semantic information from text. Such semantic information, usually extracted in the form of semantic annotations, has the potential to significantly improve the quality of free text search and retrieval.

[0003] However, the architectures of conventional information retrieval systems are not explicitly designed to take advantage of semantic annotations. In particular, semantic annotations provide the capability for describing content in terms of types and relationships, that is concepts that are not intrinsic to conventional information retrieval systems. For example, a particular document in a corpus may contain a person name “John” and a telephone number for John: “555-1234”, but not the actual word “telephone”. A person may search on that corpus using the keyword phrase “John telephone”. However, a conventional retrieval system does not find the document since the keyword “telephone” is not present. In essence, conventional information retrieval systems merely recognize keywords but not the types into which a word or phrase may be categorized or the relationships between such types.

[0004] A conventional information retrieval system is typically designed to return a ranked list of matching documents in response to a keyword search query comprising search words or tokens. In a standard implementation of such a system, an entire corpus of documents is processed in advance to build an inverted index. This inverted index maps each token to a list of occurrences of that token. A token is usually a word or a phrase; however, a token can also be a more complex entity.

[0005] Upon receiving a keyword query, the inverted index is used to compute a list of candidate documents that are potentially relevant to the query. Each of these candidate documents is assigned a rank, using a pre-designed ranking formula. The rank ordered list of candidate documents is then presented to the user. Although this technology has proven to be useful, it would be desirable to present additional improvements. The tightly integrated architecture of conventional information retrieval systems directly maps a query to storage and index structures. Consequently, it becomes difficult to exploit available semantic annotations. In conventional information retrieval systems, the available semantic annotations can only be exploited in an ad-hoc fashion by hand crafting specialized ranking formulae. Such ad-hoc ranking formulae are difficult to construct and are very often not portable across document collections. As a result, every time an information retrieval system is deployed over a new document collection, a significant amount of time and effort is required to craft a ranking formulae appropriate to that collection.

[0006] What is therefore needed is a system, a computer program product, and an associated method for exploiting semantic annotations in executing keyword queries over a collection of text documents, allowing a user to search on a corpus and locate information based on types and relationships found in the corpus by, for example, a text analysis engine. The need for such a solution has heretofore remained unsatisfied.

[0007] The present invention satisfies this need, and presents a system, a service, a computer program product, and an associated method (collectively referred to herein as “the system” or “the present system”) for exploiting semantic annotations in executing keyword queries over a collection of text documents. The present system comprises an architecture and an associated query expansion algorithm for systematically and meaningfully exploiting semantic annotations.

[0008] The present system casts semantic annotations produced by text analysis engines into a formal annotation type system. Using the annotation type system, the present system translates a keyword query into a set of queries in an intermediate query language. Each of these intermediate queries is a specific interpretation of the original keyword query. In turn, each interpretation returns a list of documents when executed over the underlying annotated document collection.

[0009] Thus, the present system replaces the conventional one-stage retrieval model (keywords directly produce result documents) with a two-stage retrieval model (keywords producing interpretations which in turn produce documents). A key advantage of the present system is that even though a complex and powerful type system is used to model semantic annotations, a user is able to continue to use simple keyword queries to locate documents. All of the complex queries against the type system are automatically generated.

[0010] The present system provides a formal algorithm for exploiting semantic annotations, as opposed to conventional ad-hoc implementations based on ranking functions, thresholds, weights, etc. Since the present system employs a keyword search interface, there is no additional burden on the user to learn complex query languages over annotated text. The present system is easily generalized to take advantage of more complex annotations such as relationship annotations and co-reference resolution annotations.

[0011] The query execution architecture of the present system separates the semantic interpretation of document content (achieved through text analysis) from the semantic interpretation of keyword queries (achieved using the query expansion algorithm of the present system). This results in a more flexible architecture. Using the present system, a set of text analytic engines can be executed over an existing document collection and the results can be seamlessly used without changing any index structure, ranking algorithm, or query evaluation system. This is difficult to achieve using a conventional monolithic information retrieval architecture.

[0012] The present system comprises a modeler for generating a type system from the outputs generated by one or more text analysis engines, an annotation type system representing concepts that can be identified in a corpus of data, and an indexer for generating an interpretation index from the type system and the output of the text analysis engines. The present system further comprises an interpreter for translating a keyword search query into one or more precise interpretations, based on matching the keywords with the values in the interpretation index.

[0013] The present system may be embodied as an annotation-enhanced text retrieval system. The present invention provides means for the user to identify a set of documents to be queried. The present invention further provides means for the user to generate a type system, either automatically through analysis of the set of documents, or as specified by the user. The present invention provides means for the user to build an interpretation index over this type system. In addition, the present system provides means for the user to invoke the interpreter to interpret keyword queries and to retrieve documents matching the generated interpretations.

[0023] The following definitions and explanations provide background information pertaining to the technical field of the present invention, and are intended to facilitate the understanding of the present invention without limiting its scope:

[0024] Entity Concept: Any semantic concept, instances of which are mentioned one or times in a document corpus, recognized, and extracted by a text analysis engine, is called an entity concept. For instance, given a collection of customer service reports mentioning names and contact information for various customers, examples of entity concepts include Persons, Organizations, Phone Numbers, Locations, etc.

[0025] Relationship Concept: A relationship between two or more entity concepts that is explicitly represented at least once in a given document corpus is called a relationship concept. For instance, given the entity concepts listed above, the relationship “Contact Number” that associates a given Person entity with a Phone Number entity that represents that person's phone number is an example of a Relationship Concept.

[0026] Type: A type is any formal representation of an entity or relationship concept using the modeling concepts of some standard data model. For instance, using the relational data model, a type can be viewed as a relation whereas using an object oriented data model, a type can be viewed as a “class”. The exact representation for a type is specific to a particular embodiment of this invention.

[0027] Attribute: Every type is associated with a set of one or more attributes that define the values associated with objects of that type. For instance, a Person type could be associated with attributes First name and Last name so that every object of that Person type has First name and Last name values.

[0028] FIG. 1 portrays an exemplary overall environment in which a system, a computer program product, and associated method (the “system 10”) for exploiting semantic notations in executing keyword queries over a collection of documents according to the present invention may be used. System 10 comprises a software programming code or a computer program product that is typically embedded within, or installed on a host server 15. Alternatively, system 10 can be saved on a suitable storage medium such as a diskette, a CD, a hard drive, or like devices.

[0029] Users, such as remote Internet users, are represented by a variety of computers such as computers 20, 25, 30, and can access the host server 15 through a network 35 by means of, for example, a keyword search user interface (UI) 40. By utilizing a keyword search application such as the keyword search UI 40, a user can search data stored in store/index 45.

[0030] The store/index 45 can support standard keyword queries over documents as well as more complex precise queries (e.g., using XPath) over annotations. In one embodiment, the store/index 45 comprises multiple individual data management engines. One data management engine comprises an XPath-capable XML data store for the annotations and another data management engine comprises a standard information retrieval engine for keyword queries over the documents.

[0031] Computers 20, 25, 30 each comprise software that allows the user to interface securely with the host server 15. The host server 15 is connected to network 35 via a communications link 55 such as a telephone, cable, or satellite link. Computers 20, 25, 30, can be connected to network 35 via communications links 60, 65, 70, respectively. While system 10 is described in terms of network 35, computers 20, 25, 30 may also access system 10 locally rather than remotely. Computers 20, 25, 30 may access system 10 either manually, or automatically through the use of an application such as the keyword search UI 40. While system 10 is described in terms of the keyword search UI 40, it should be clear that computers 20, 25, 30 can access a keyword search interface implemented on the host server 15 via network 35.

[0032] FIG. 2 illustrates a high-level hierarchy of system 10. System 10 comprises an interpretation index 205, an indexer 210, a type system 215, a modeler 220, and an interpreter 225. During off-line processing, the text analysis engines 50 execute a suite of pre-selected text analysis engines over a document collection in store/index 45, producing annotations for the analyzed documents. The annotations produced by the text analysis engines 50 are serialized into a meaningful format that allows for efficient indexing and query-based retrieval.

[0033] The serialized annotations and the original documents are stored in the store/index 45. For instance, annotations can be serialized into XML documents and stored in store/index 45; in this case store/index 45 is capable of efficiently supporting XPath queries. In addition to serialization, annotations are cast into a formal type system 215 and the interpretation index 205 is built over the type system 215.

[0034] Upon receiving a keyword query from the keyword search UI 40, the interpreter 225 matches the keyword query with the interpretation index 205 to generate a set of intermediate queries. For instance, user 230 formulates a search with two keyword queries, k1 and k2. System 10 interprets the query as five intermediate queries q1, q2, q3, q4, and q5. System 10 executes each of these intermediate queries over the store/index 45 to produce a list of documents. The interpreter 225 merges these individual lists and produces a single output list that is presented to user 230. While system 10 is described for illustration purpose only with respect to intermediate queries expressed in SQL-like syntax, it should be clear that system 10 is applicable as well to, for example, any other query language of similar or higher expressive power.

[0035] An exemplary scenario comprising service reports from a customer relationship management database of an auto manufacturer illustrates operation of system 10. Table 1 lists exemplary text analysis engines 50 that are executed over the exemplary database. Each annotation produced by these exemplary text analysis engines 50 is a structured object. Modeler 220 represents the output of the text analysis engines 50 as types, with each type having one or more named attributes.

[0036]

TABLE 1
Exemplary text analysis engines and their associated purpose in
extracting annotations from the exemplary data collection.
Text Analysis Engine	Purpose
Named-Entity Person	Identifies names of persons occurring in text
Named-Entity	Identifies names of organizations occurring in text
Organization
Named-Entity	Identifies names of cities or other locations
City/Location	occurring in the text
Contacted	Links a Person p with an Organization o if the
	text indicates that p contacted o
Partner	Identifies those organizations that are partners
	of the auto manufacturer and lists an
	associated department for that partner
Topic	Identifies service reports that refer to engine
	problems or brake problems

[0037] FIG. 3 illustrates an exemplary type system 300 that describes the annotation objects produced by the exemplary text analysis engines 50 when executed on the customer relationship management database. Each of the text analysis engines 50 analyzes the customer relationship management database for different concepts; i.e., department, city, organization name, person name, city name, engine problem, and brake problem. Table 2 illustrates exemplary instances of this type system including the strings that are generated by the text analysis engines 50.

[0038]

TABLE 2
Exemplary strings generated by the text analysis engines for an
exemplary customer relationship management database.
	Type	Attribute	String	Values
	Partner	Department	String 1	Engine
				Axle
				Brake
				Tires
	City	Name	String 2	LA
				Boston
				NY
	Organization	Name	String 3	Firestone
				GM
				National Ins.
	Person	Name	String 4	Jane
				Sue
				John Smith
	City	Name	String 5	San Jose, CA
				New York
				Boston, MA
	Engine Problem	Topic	String 6	fuel injection
		words		cylinder
	Brake Problem	Topic	String 7	brake shoes
		words		brake pads
				master cylinder

[0039] The text analysis engines 50 generate string 1, 305, string 2, 310, string 3, 315, string 4, 320, string 5, 325, string 6, 330, and string 7, 335 (collectively referenced as strings 340). Modeler 220 analyzes the outputs of the text analysis engines 50 and generates the type system 300 shown in FIG. 3. Modeler 220 assigns attributes to each of the strings 340 as shown in Table 2. Each of the strings 340 is assigned to an entity concept or a relationship concept. A relationship concept relates strings or entity concepts. In FIG. 3, entity concepts comprise organization 345, person 350, city 355, EngineProblem 360, and BrakeProblem 365. Relationship concepts comprise partner 370 and contacted 375. Values of the strings are referenced as attribute values.

[0040] Indexer 210 builds an interpretation index 205 (I) over the exemplary set of all names of types (e.g., Person, Organization, EngineProblem, . . . ), attribute names (e.g., city, department, . . . ), and attribute values (e.g., GM, Jane, National Ins., . . . ), such that given a keyword w, I(w) returns one or more of the following:

• • [0041] [type T]: w matches the name of a type T in the object model, and
  • [0042] [val T.y]: w matches the value of an attribute y of type T.

[0043] In the preceding definition, string matches can be fuzzy. In particular, interpreter 225 can employ standard information retrieval techniques for approximate matches such as, for example, stemming, stop-word elimination, relaxed capitalization, substring matches, synonym expansion, etc.

[0044] Depending on the precise implementation, interpreter 225 determines exemplary matches of keywords as shown in Table 3.

[0045]

TABLE 3
Exemplary matches shown are generated by interpreter 225 for
keywords in the exemplary type system of the exemplary
customer relationship management database.
	Keyword	Matches
	National	[val Organization.name]
	Jane	[val Person.name]
	engine	[type EngineProblem]
	engine	[val Partner.dept]
	LA	[val Partner.city]
	LA	[val City.name]

[0046] Interpreter 225 tokenizes a query provided by user 230 to generate one or more tokens and attempts to match those tokens with the interpretation index 205. For instance, consider the keyword query “Jane GM”. Interpreter 225 generates two tokens “Jane” and “GM” and probes the interpretation index 205 for matches. Interpreter 225 identifies matches in [val Person.name] and [val Organization.name] respectively. Furthermore, each token can be treated as a keyword without imposing any additional semantics. The interpreter 225 denotes this default match using the notation [kwd Jane] and [kwd GM] respectively.

[0047] Interpreter 225 generates queries by taking one or more possible combinations of matches for each keyword. For this example, interpreter 225 generates the following queries shown below in SQL-like syntax:

Query (1,1): return documents that mention person Jane and organization GM.

• • [0048] select d
  • [0049] from Document d, Person p, Organization o
  • [0050] where d=p.doc=o.doc AND
    • [0051] MATCH(p.name, Jane) AND MATCH(o.name, GM)
      Query (1,2): return documents that mention person Jane and keyword “GM”.
  • [0052] select d
  • [0053] from Document d, Person p
  • [0054] where d=p.doc AND MATCH(p.name, Jane) AND SEARCH(d, “GM”)
    Query (2,1): return docs that match keyword Jane and organization GM.
  • [0055] select d
  • [0056] from Document d, Organization o
  • [0057] where d=o.doc AND MATCH(o.name, GM) AND SEARCH(d, “Jane”)
    Query (2,2): return docs that match keywords “Jane GM”.
  • [0058] select d
  • [0059] from Document d, Person p
  • [0060] where SEARCH(d, “Jane GM”)

[0061] Query (2,2) is a conventional keyword search query. In general, since a [kwd] match exists for every query token, the query expansion technique of interpreter 225 generates the standard keyword search query as a special case for all queries. Thus, the interpretations produced by the query expansion technique of the present invention subsume a standard retrieval engine that is based purely on keyword matches.

[0062] Interpreter 225 makes additional use of the type system 300 represented in FIG. 3 to derive more sophisticated interpretations of the keyword query. Query (1,1) was generated using the matches [val Person.name] and [val Organization.name]. The type system 300 comprises a type “Contacted”; “Contacted comprises attributes of type “Person” and “Organization”. Interpreter 225 generates a modified version of Query (1,1) using the type “Contacted” and replacing each “Person” with Contacted.initiator and “Organization” with Contacted.recipient. The generated query becomes:

Query (1,1)′: return docs that mention person Jane contacted organization GM.

• • [0063] select d
  • [0064] from Document d, Contacted c
  • [0065] where d=c.initiator.doc=c.recipient.doc AND
  • [0066] MATCH(c.initiator.name, Jane) AND MATCH(c.recipient.name, GM)

[0067] In the exemplary type system 300 shown in FIG. 3, there is only one type “Contacted” with the requisite characteristics to replace “Person” and “Organization”. In general, there can be more than one such type. Furthermore, interpreter 225 can extend this technique to look for higher-order relationships (as opposed to an immediate ancestor) in the type graph of a type system 215. Interpreter 225 uses a “shared ancestor rule” to discover higher-order relationships.

[0068] The shared ancestor rule for query generation is as follows: Given a query “k₁ k₂” such that keyword k₁ has a match of the form [val T1.x], keyword k₂ has a match of the form [val T2.y], and there exists a type T with attributes “a” and “b” such that T.a is of type T1 and T.b is of type T2, interpreter 225 can generate the following query:

• • [0069] select d
  • [0070] from Document d, T t
  • [0071] where t.a.doc=t.b.doc=d AND
    • [0072] MATCH(t.a.x, k₁) AND MATCH(t.b.y, k₂)

[0073] As another example, consider a keyword “Engine LA”. Interpreter 225 generates tokens for the keyword and identifies matches as follows:

• • [0074] Engine: type EngineProblem
    • [0075] val Partner.dept
    • [0076] kwd Engine
  • [0077] LA: val City.name
    • [0078] val Partner.city
    • [0079] kwd LA

[0080] Interpreter 225 generates an exemplary query for keyword “Engine LA” as follows:

Query (2,2): return docs that mention an engine partner and a partner located in LA.

• • [0081] select d
  • [0082] from Document d, Partner p1, Partner p2
  • [0083] where d=p1.org.doc=p2.org.doc AND
    • [0084] MATCH(p1.dept, Engine) AND MATCH(p2.city, LA)

[0085] Interpreter 225 employs a type-merging rule to merge the instances of “Partner” (p1 and p2) into a single “Partner” instance, generating the following query:

Query (2,2)′: return docs that mention an engine partner located in LA.

• • [0086] select d
  • [0087] from Document d, Partner p
  • [0088] where d=p.org AND MATCH(p.dept, Engine) AND MATCH(p.city, LA)

[0089] More generally, the type-merging rule can be stated as follows: Given a query “k₁ k₂” such that keyword k₁ has a match of the form [val T.x] and keyword k₂ has a match of the form [val T.y], interpreter 225 can generate a query:

• • [0090] select d
  • [0091] from Document d, T t
  • [0092] where t.doc=d AND MATCH(t.x, k₁) AND MATCH (t.y, k₂)

[0093] FIG. 4 illustrates a method 400 of system 10 in generating a type system for a collection of documents comprising annotations and executing a query against that collection of documents. Each of the text analysis engines 50 generates one or more character strings per document analyzed by the text analysis engine 50. The modeler 220 models output of the text analysis engines 50 to generate the type system 215 (step 500, further described in FIG. 5). Indexer 210 builds an interpretation index 205 from the type system 215 (step 600, further described in FIG. 6). Interpreter 225 considers a keyword query provided by user 230 and generates a set of candidate interpretations for the keyword query (step 700, further described in FIG. 7). Interpreter 225 executes one or more candidate interpretations against the type system 215 represented in the interpretation index 205 (step 800, further described in FIG. 8). The interpreter 225 retrieves matching documents from the store/index 45 (step 405). Step 500 and step 600 comprise an “offline” document analysis process that is performed prior to query execution by system 10. Step 700, step 800, and step 405 are performed “online” during query execution by system 10.

[0094] The type system 215 is a structure representing annotations generated by the text analysis engines 50 from data in the store/index 45. Annotations are, for example, strings representing data found in a document. The type system 215 comprises concepts. Concepts are entity concepts or relationship concepts. The relationship concept describes a relationship between selected entity concepts. For example, a “contact” relationship concept may describe a relationship between a person entity concept and a phone number entity concept. The type system 215 provides a structure for the annotations that enables complex queries against data in the store/index 45. The type system 215 is a specific instance of a model for annotations of the data in store/index 45.

[0095] FIG. 5 illustrates a method 500 by which modeler 220 generates the type system 215 from annotations provided by the text analysis engines 50. Method 500 can be performed manually by a human, automatically by an application, or manually with assistance from an application.

[0096] Modeler 220 selects output of one of the text analysis engines 50 (step 505). The output of each of the text analysis engines 50 comprises one or more concepts. Modeler 220 selects an initial concept for the selected output (step 510).

[0097] Modeler 220 generates a type to represent the selected concept (step 515), with one type per concept. Generating a type comprises naming the type as an entity or a relationship and identifying one or more attributes for the type. The modeler 220 determines whether the selected concept is a relationship concept (decision step 520). For example, a selected concept may be an entity concept Person; another selected concept may be an entity concept Phone number”. Person and Phone number can be related by a relationship concept Contact. If the selected concept is a relationship (decision step 520), modeler 220 identifies the relationship concept and associated entity concepts (step 525). For example, modeler 220 may identify “contact” as a relationship concept, with associated entity concepts as person and phone number.

[0098] After identifying the relationship concept and associated entity concepts (step 525) or if the selected concept is not a relationship (decision step 520), modeler 220 determines whether additional concepts remain for processing from the selected output of the selected text analysis engine 50 (decision step 530). If additional concepts remain for processing, modeler 220 selects a next concept (step 535) and repeats step 515 through step 530 until no concepts from the selected output of the text analysis engine 50 remain for processing.

[0099] Modeler 220 determines whether additional outputs of the selected text analysis engines 50 remain for processing (decision step 540). If additional outputs remain, modeler 220 selects a next output for a text analysis engine 50 (step 545). The selected output can be from the same text analysis engine 50 as just processed or another text analysis engine 50. Modeler 220 repeats step 510 through step 545 until no additional outputs remain for processing (decision step 540). Modeler 220 outputs the generated type system 215 (step 550).

[0100] FIG. 6 illustrates a method 600 by which indexer 210 generates an interpretation index 205. Input to indexer 210 is the output of the text analysis engines 50 and the type system 215. Indexer 210 selects an output of the text analysis engine 50 (step 605). Indexer 210 tokenizes strings in the selected output (step 610). Indexer 210 selects a token from the tokenized strings in the selected output (step 615). The indexer places an entry in the interpretation index that maps the selected token to the type in the type system 215 that represents the text analysis engine output selected in step 605.

[0101] Indexer 210 determines whether additional tokens remain for analysis (decision step 625). If yes, indexer 210 selects a next token (step 630) and repeats step 620 through step 630 until no additional tokens remain for processing.

[0102] Indexer 210 determines whether additional outputs from text analysis engines 50 remain for processing (decision step 635). If yes, indexer 210 selects a next output of a text analysis engine 50 (step 640) and repeats step 610 through step 640 until no additional outputs remain for processing. Indexer 210 outputs the generated interpretation index 205 (step 645).

[0103] FIG. 7 illustrates a method 700 by which interpreter 225 generates one or more candidate query interpretations from a keyword query. Interpreter 225 tokenizes a keyword query (step 705). Interpreter 225 selects a keyword token (step 710) and consults the interpretation index 205 to obtain a match for the keyword token (step 715). Interpreter 225 determines whether additional tokens remain for processing (decision step 720). If yes, interpreter 225 selects a next keyword token and repeats step 715 through step 725 until no additional keyword tokens remain for processing.

[0104] Interpreter 225 calculates the Cartesian product (in other words, all possible combinations) of the generated matches (step 730). Interpreter 225 selects a combination from the Cartesian product (step 735). Interpreter 225 generates a specific candidate interpretation for the selected combination (step 740). Interpreter 225 determines whether additional combinations remain for processing (decision step 745). If yes, interpreter 225 selects a next combination (step 750) and repeats step 740 through step 750 until no additional combinations remain for processing. Interpreter 225 outputs candidate query interpretations (step 755).

[0105] FIG. 8 illustrates a method 800 by which interpreter 225 generates a specific candidate interpretation for a keyword query. In the embodiment described in this invention, interpretations are represented using a SQL-like syntax. Therefore, an interpretation comprises a “select” clause, a “from” clause, and a “where” clause. Interpreter 225 generates a candidate interpretation with a select clause and a from clause (step 805):

• • [0106] select d
  • [0107] from Document d

[0108] For each type name occurring in any of the type or value matches for a selected keyword token, interpreter 225 adds an entry to the from clause (step 810). For example, referring to query (1,1) previously discussed, the candidate query becomes:

• • [0109] select d
  • [0110] from Document D, Person p, Organization o

[0111] For each value match, interpreter 225 adds a match predicate in the where clause (step 815). The match predicate comprises one or more operands. One operand is a variable for a corresponding type, followed by a “.” and the name of the attribute in the value match. Another operand is a query token that corresponds to the value match. Referring again to exemplary query (1,1), the candidate query becomes:

• • [0112] select d
  • [0113] from Document D, Person p, Organization o
  • [0114] where
  • [0115] MATCH(p.name, Jane) AND MATCH(o.name, GM)

[0116] For each keyword match, interpreter 225 adds a search predicate to the where clause (step 820). Referring to exemplary query (2,1), the candidate query becomes:

• • [0117] select d
  • [0118] from Document d, Organization o
  • [0119] where
  • [0120] MATCH(o.name, GM) AND SEARCH(d, “Jane”)

[0121] For each type in the from clause, interpreter 225 equates doc attributes to d to ensure that all the concepts involved in the interpretation occur in the same document. Referring to exemplary query (1,1), the candidate query becomes:

• • [0122] select d
  • [0123] from Document d, Person p, Organization o
    • [0124] where d=p.doc=o.doc AND
    • [0125] MATCH(p.name, Jane) AND MATCH(o.name, GM)

[0126] Referring to exemplary query (2,1), the candidate query becomes:

• • [0127] select d
  • [0128] from Document d, Organization o
  • [0129] where d=o.doc AND MATCH(o.name, GM) AND SEARCH(d, “Jane”)

[0130] An exemplary pseudocode for the query expansion process performed by the interpreter 225 is as follows:

[0131]

	INPUT (keyword query q = { k1, ..., kn }, interpretation index I)
	ForEach i = 1.. n
	compute mi = I(ki) U { [kwd ki] }
	END ForEach
	generated = { }
	ForEach c = (c1, c2, ..., cn) ∈ (m1 × m2 × .... × mn)
	fromEntries = {“Document d”}
	predicates = { }
	keywords = { }
	ForEach i = 1..n
	ci = [type T] => fromEntries = fromEntries U {T xi} AND
	predicates = predicates U {xi.doc = d}
	ci = [val T.y] => fromEntries = fromEntries U {T xi} AND
	predicates = predicates U {xi.doc = d, MATCH(xi.y, ki)}
	ci = [kwd ki] => keywords = keywords U {ki}
	END ForEach
	selectClause = “select d”
	/* construct a valid from clause using the
	* elements of the fromEntries set
	*/
	fromClause = generateFromClause(fromEntries)
	/* construct a valid where clause by AND'ing
	* together all the predicates
	*/
	whereClause = generateWhereClause(predicates, keywords)
	/* construct a valid query using the select,
	* from, and where clauses
	*/
	currentQuery = generateQuery(selectClause,
	fromClause, whereClause)
	generated = generated U {currentQuery}
	END ForEach
	OUTPUT generatedQueries

[0132] It is to be understood that the specific embodiments of the invention that have been described are merely illustrative of certain applications of the principle of the present invention. Numerous modifications may be made to the system and method for exploiting semantic annotations in executing keyword queries over a collection of text documents described herein without departing from the spirit and scope of the present invention. Moreover, while the present invention is described for illustration purpose only, in relation to documents or texts, it should be clear that the invention is similarly applicable to, for example, any type of objects. Moreover, while the present invention is described for illustration purpose only, in relation to a network such as, for example, the Internet, it should be clear that the invention is applicable as well to, for example, local access by users.