CA2596279A1 - Web query classification - Google Patents
Web query classification Download PDFInfo
- Publication number
- CA2596279A1 CA2596279A1 CA002596279A CA2596279A CA2596279A1 CA 2596279 A1 CA2596279 A1 CA 2596279A1 CA 002596279 A CA002596279 A CA 002596279A CA 2596279 A CA2596279 A CA 2596279A CA 2596279 A1 CA2596279 A1 CA 2596279A1
- Authority
- CA
- Canada
- Prior art keywords
- query
- classification
- phrase
- query phrase
- category
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
- G06F16/353—Clustering; Classification into predefined classes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
Abstract
A query phrase may be automatically classified to one or more topics of interest (e.g., categories) to assist in routing the query phrase to one or more appropriate backend databases. A selectional preference query classification technique may be used to classify the query phrase based on a comparison between the query phrase and patterns of query phrases.
Additionally, or alternatively, a combination of query classification techniques may be used to classify the query phrase. Topical classification of a query phrase also may be used to assist a search system in delivering auxiliary information to a user who entered the query phrase. Advertisements, for instance, may be tailored based on classification rather than query keywords.
Additionally, or alternatively, a combination of query classification techniques may be used to classify the query phrase. Topical classification of a query phrase also may be used to assist a search system in delivering auxiliary information to a user who entered the query phrase. Advertisements, for instance, may be tailored based on classification rather than query keywords.
Description
WEB QUERY CLASSIFICATION
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No.
60/647,424, filed January 28, 2005, and titled WEB QUERY CLASSIFICATION, which is incorporated by reference in its entirety.
TECHNICAL FIELD
This description relates to classifying search queries.
BACKGROUND
A query phrase may be classified into a particular category. The query phrase may be classified manually by a human editor or through an automated comparison of the query phrase against a list of query phrases previously classified manually by a human editor. The query phrase also may be classified automatically by a system that has learned, from a training set of classified query phrases, to distinguish characteristics of query phrases in order to classify a particular query phrase.
SUMMARY
In a general aspect, satisfaction of a search responsive to a query is enabled based on classification of the query. A query phrase is received from user input.
The received query phrase is parsed into constituent parts. A pattenl that is associated with at least one category is accessed from classification information stored in a coniputer storage medium that includes patterns of query phrases. Whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern is determined. Based on a determination that a constituent part parsed from the received query plirase corresponds to at least a subportion of an accessed pattern, the category that is associated with the pattern also is associated with the query phrase or the constituent part. At least one search resource for satisfying the query phrase based on the associated category is identified.
Implementations may include one or more of the following features. For example, routing of the query phrase to the at least one identified search resource may be enabled. Associating the category may include associating the category with the query phrase. Associating the category may include associating the category with the constituent part. More than one category may be associated with the query phrase or the constituent part.
Based on the query phrase, a search result may be received from the at least one identified search resource and presentation of the at least one search result to the user may be enabled.
The category associated with the search query may be compared with attributes associated with the multiple search resources, such that routing the query phrase to at least one search resource may include modifying the query phrase and routing a modified version of the query phrase to a subset of multiple search resources based on results of the comparison. Modifying the query phrase may include adding words to the query phrase, eliminating words from the query phrase, and/or re-ordering words in the query phrase.
An advertisement associated with at least one of the categories associated with the query phrase may be determined and presentation of the advertisement to the user may be enabled.
A selectional preference query classification technique may be trained. The training may include receiving a training query phrase including constituent parts, parsing the training query phrase into at least one constituent part, receiving additional training query phrases having at least one constituent part in common with the training query phrase, recognizing a pattern of training query phrases having at least one common constituent part, detennining a category associated with the at least one common constituent part, associating the pattern of training query phrases with the category associated with the at least one common constituent part, and using the pattern to categorize query phrases. A constituent part may include an individual word, a subportion of the training query phrase, and/or the entire training query phrase.
A query phrase may be classified using a manual query classification technique and/or a supervised machine learning query classification technique. The results of the query classification techniques may be compared and the query phrase may be classified using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques. A category for the query phrase may be determined using more than two query classification tecliniques. The query phrase may be classified using the classification arbiter and based on the classification determined by a majority of the query classification techniques. The classification arbiter may determine the classification of the query phrase based on a confidence in the classification of the query phrase that resulted from using a query classification technique and an overall classification metric of the query classification technique. The query phrase may be classified using the classification arbiter and based on both the classification determined by a majority of the query classification teclmiques and a determination of the classification based on a confidence in the classification of the query phrase that resulted from using a query classification technique and the overall classification metric of the query classification technique.
The manual query classification technique may be used as the seed for the selectional preference and supervised machine learning query classification techniques.
In another general aspect, a query classification technique is trained. A
training query phrase that includes constituent parts is received. The training query phrase is parsed into at least one constituent part. Additional training query phrases having at least one constituent part in common with the training query phrase are received. A
pattern of training query phrases having at least one common constituent part is recognized. A
category associated with the at least one common constituent part is determined. The pattern of training query phrases is associated with the category associated with the at least one common constituent part. The pattern is stored in a computer readable medium as classification information.
Implementations may include one or more of the features noted above or one or more of the following features. For example, constituent parts may include individual words, smaller phrases within the query phrase, and/or the entire query phrase.
Implementations of any of the techniques described may include a method or process, an apparatus or system, or computer software on a computer-accessible medium.
The details of particular implementations are set forth below. Other features will be apparent from the description and drawings, and from the claims.
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No.
60/647,424, filed January 28, 2005, and titled WEB QUERY CLASSIFICATION, which is incorporated by reference in its entirety.
TECHNICAL FIELD
This description relates to classifying search queries.
BACKGROUND
A query phrase may be classified into a particular category. The query phrase may be classified manually by a human editor or through an automated comparison of the query phrase against a list of query phrases previously classified manually by a human editor. The query phrase also may be classified automatically by a system that has learned, from a training set of classified query phrases, to distinguish characteristics of query phrases in order to classify a particular query phrase.
SUMMARY
In a general aspect, satisfaction of a search responsive to a query is enabled based on classification of the query. A query phrase is received from user input.
The received query phrase is parsed into constituent parts. A pattenl that is associated with at least one category is accessed from classification information stored in a coniputer storage medium that includes patterns of query phrases. Whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern is determined. Based on a determination that a constituent part parsed from the received query plirase corresponds to at least a subportion of an accessed pattern, the category that is associated with the pattern also is associated with the query phrase or the constituent part. At least one search resource for satisfying the query phrase based on the associated category is identified.
Implementations may include one or more of the following features. For example, routing of the query phrase to the at least one identified search resource may be enabled. Associating the category may include associating the category with the query phrase. Associating the category may include associating the category with the constituent part. More than one category may be associated with the query phrase or the constituent part.
Based on the query phrase, a search result may be received from the at least one identified search resource and presentation of the at least one search result to the user may be enabled.
The category associated with the search query may be compared with attributes associated with the multiple search resources, such that routing the query phrase to at least one search resource may include modifying the query phrase and routing a modified version of the query phrase to a subset of multiple search resources based on results of the comparison. Modifying the query phrase may include adding words to the query phrase, eliminating words from the query phrase, and/or re-ordering words in the query phrase.
An advertisement associated with at least one of the categories associated with the query phrase may be determined and presentation of the advertisement to the user may be enabled.
A selectional preference query classification technique may be trained. The training may include receiving a training query phrase including constituent parts, parsing the training query phrase into at least one constituent part, receiving additional training query phrases having at least one constituent part in common with the training query phrase, recognizing a pattern of training query phrases having at least one common constituent part, detennining a category associated with the at least one common constituent part, associating the pattern of training query phrases with the category associated with the at least one common constituent part, and using the pattern to categorize query phrases. A constituent part may include an individual word, a subportion of the training query phrase, and/or the entire training query phrase.
A query phrase may be classified using a manual query classification technique and/or a supervised machine learning query classification technique. The results of the query classification techniques may be compared and the query phrase may be classified using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques. A category for the query phrase may be determined using more than two query classification tecliniques. The query phrase may be classified using the classification arbiter and based on the classification determined by a majority of the query classification techniques. The classification arbiter may determine the classification of the query phrase based on a confidence in the classification of the query phrase that resulted from using a query classification technique and an overall classification metric of the query classification technique. The query phrase may be classified using the classification arbiter and based on both the classification determined by a majority of the query classification teclmiques and a determination of the classification based on a confidence in the classification of the query phrase that resulted from using a query classification technique and the overall classification metric of the query classification technique.
The manual query classification technique may be used as the seed for the selectional preference and supervised machine learning query classification techniques.
In another general aspect, a query classification technique is trained. A
training query phrase that includes constituent parts is received. The training query phrase is parsed into at least one constituent part. Additional training query phrases having at least one constituent part in common with the training query phrase are received. A
pattern of training query phrases having at least one common constituent part is recognized. A
category associated with the at least one common constituent part is determined. The pattern of training query phrases is associated with the category associated with the at least one common constituent part. The pattern is stored in a computer readable medium as classification information.
Implementations may include one or more of the features noted above or one or more of the following features. For example, constituent parts may include individual words, smaller phrases within the query phrase, and/or the entire query phrase.
Implementations of any of the techniques described may include a method or process, an apparatus or system, or computer software on a computer-accessible medium.
The details of particular implementations are set forth below. Other features will be apparent from the description and drawings, and from the claims.
DESCRIPTION OF DRAWINGS
Fig. 1 is a block diagram of a communications system capable of classifying a query phrase and routing the query phrase to a backend database related to the query phrase classification.
Fig. 2 is a flow chart of a process for performing a search based on classification of a query phrase using a selectional preference query classification teciznique.
Fig. 3 is a block diagranl illustrating an example of performing a search based on classification of a query plirase using a selectional preference query classification technique.
Fig. 4 is a flow chart of a process for training a selectional preference query classification technique.
Fig. 5 is a block diagram illustrating an example of training a selectional preference query classification technique for a particular pattern.
Fig. 6 is a block diagram illustrating an example of perforining a search for a query phrase based on a classification of the query phrase using a combination of query classification techniques.
Like reference synlbols in the various drawings indicate like elements.
DETAILED DESCRIPTION
Search engines, both for the Web and for enterprises, may automatically route an incoming query phrase to several specialized backend databases and may merge the search results received from those databases to create a merged listing. To receive meaningful search results, the inetasearch system selects a subset of all available backend databases, based, for instance, on the relative appropriateness of each database to the query phrase. Being selective with routing decisions may result in a relatively high ratio of relevant results, which results in more efficient and less costly processing when compared with results that follow from sending every query phrase to every backend database and the relatively low ratio of relevant results following therefrom.
Techniques are described for automatically classifying a query phrase among one or more topics of interest (e.g., categories) and using those topics of interest to assist in routing the query phrase to an appropriate subset of available backend databases. A
selectional preference query classification technique may be used to select a subset of backend databases (or other searchable resources or search processes) based on a coinparison between a query phrase and patterns of query phrases.
Additionally, or alternatively, a combination of query classification techniques may be used to classify a query phrase. Techniques also are described for using topical classification of a query phrase to assist a search system in delivering auxiliary information to a user who entered the query phrase. Advertisements, for instance, may be tailored based on classification rather than query keywords.
Referring to Fig. 1, a communications system 100 is configured to classify a query phrase and, based on the query phrase classification, route the query phrase to a backend database related to the query phrase classification. More particularly, the communications system 100 is configured to deliver and exchange messages between a client system 110 and a search system 120 through a delivery networlc 115 to classify a user entered query phrase into a topical category and provide search results received from a backend database to which the query phrase is routed and which is related to the query phrase classification.
Each of the client system 110 and the search system 120 may be a general-purpose computer (e.g., a personal computer, a desktop computer, or a laptop computer) configured to respond to and execute instructions in a defined manner. Other examples of the client system 110 and the search system 120 include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination thereof capable of responding to and executing instructions. The client system 110 also may be a personal digital assistant (PDA), a communications device, such as a mobile telephone, or a mobile device that is a combination of a PDA
and communications device.
The client system 110 also includes a communication application 112 and is configured to use the communication application 112 to establish a conununication session with the search system 120 over the delivery network 115. The communication application 112 may be, for example, a browser or another type of communication application that is capable of accessing the search system 120. In another example, the communication application 112 may be a client-side application configured to communicate with the search system 120. The client system 110 is configured to send to the searcll system 120 requests for search results (e.g., a query phrase entered by a user).
The client system 110 also is configured to receive search results from the search system 120 and to present the received search results to the user.
The delivery networlc 115 provides a direct or indirect communication link between the client system 110 and the search system 120, irrespective of physical separation. Exainples of a delivery network 115 include the In.ternet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., PSTN
("Public Switched Telephone Network"), ISDN ("Integrated Services Digital Network"), and DSL ("Digital Subscriber Line") including various fonns of DSL such as SDSL
("Single-line Digital Subscriber Line"), ADSL ("Asymmetric Digital Subscriber Loop), HDSL ("High bit-rate Digital Subscriber Line"), and VDSL ("Very high bit-rate Digital Subscriber Line)), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data.
The delivery network 115 includes communication pathways 117 that enable the client system 110 and the search system 120 to communicate with the delivery networlc 115. Each of the communication pathways 117 may include, for example, a wired, wireless, virtual, cable or satellite communications pathway.
The search system 120 may receive instructions from, for example, a software application, a program, a piece of code, a device, a coinputer, a computer system, or a combination thereof, which independently or collectively direct steps, as described herein. The search system 120 includes a communication application 122 that is configured to enable the search system 120 to communicate with the client system 110 through the delivery network 115.
The search system 120 may be a host system, such as an Internet service provider that provides a search service to subscribers. In another example, the search system 120 may be a system that hosts a web site that provides search services to the general public.
The search system 120 also may be referred to as a search engine or a search service.
In general, the search system 120 may be configured to classify a user entered query phrase into a topical category and provide search results received from a backend database to which the query pllrase is routed and which is related to the query phrase classification.
More particularly, the search system 120 includes selectional preference unit configured to classify a query phrase. Selectional preference unit 124 includes classification process code segment 124a, classification information data store 124b and training process code segment 124c.
Classification process code segment 124a may be configured to receive a query phrase entered by a user at client 110. For example, code segment 124a may receive the query phrase "BMW wheels." Code segment 124a may be further configured to detennine and associate a category with the received query phrase. To do so, code segment 124a may access classification information data store 124b.
Classification information data store 124b may be configured to store information related to patterns of query phrases and associated categories. A query phrase may include constituent parts, where a constituent part may be an individual word, a smaller phrase of more than one word within the query phrase or the entire query phrase. Data store 124b may be configured to store a category associated with a particular pattern of query phrases having the same, or similar, constituent parts. In some implementations, data store 124b may be configured to store an association between a category, or some other descriptive or definitional infonnation, and a particular individual constituent part.
For example, data store 124b may store a pattern of query phrases that include a particular automobile manufacturer plus the word "wheels." The pattern may be associated with the category "automobile." Furthermore, in some impleinentations, the constituent part "wheels" also may be associated with the automobile category.
Training process code segment 124c may be configured to detect a pattern of query phrases, associate a detected pattern with a category and store the detected pattern and associated category information in data store 124b, as described in detail below.
Code segment 124c may be executed for the purpose of setting up initial classification infornaation to be used by code segment 124a to classify a query phrase. For example, in keeping with the above noted example used with respect to data store 124b, code segment 124c may be executed to detect a pattern of query phrases that include an automobile manufacturer plus the word "wheels" based on a series of query phrases, such as Ford plus wheels or Nissan plus wheels.
In some implementations, code segment 124c may be configured to determine whether a relationship between a detected pattern and a category is strong enougli to warrant associating the detected pattern with the category and storing the information in data store 124b for use in categorizing future query phrases. If the strength of the relationsllip satisfies a threshold, the detected patteni and associated category may be useful in categorizing future query phrases and will be stored in data store 124b. If the strength of the relationship does not satisfy the threshold, the detected pattern may not be useful in categorizing future query phrases. In this example, the detected pattern may not be associated with the category, nor stored in data store 124b for future use.
Alternatively or additionally, if a different category exists with which the detected pattern may be associated, code segment 124c may associate the detected pattern with the different category, and store the information in data store 124b, if there is a stronger (and more useful) relationship between the detected pattern and the different category.
Code segment 124c also may be executed at predetermined intervals, or upon the happening of a particular event (e.g., a user request) to update the classification information stored in data store 124b. For example, a new automobile manufacturer may come into the market, such as Renner Automotive. In this example, code segment 124c may be executed to update the classification information within data store 124b to include Renner plus the word "wheels" in the detected pattern of automobile manufacturer plus the word "wheels" because "Renner" is an automobile manufacturer.
Furthermore, code segment 124c may be configured to associate the new entry with the automobile category that is associated with the detected pattern. In some iinplementations, code segment 124c may be configured to associate the word "Renner"
with the automobile category and/or definitional information, such as, for example, to indicate that the word "Renner" refers to an automobile manufacturer.
The search system 120 may determine that Renner is an automobile manufacturer in several ways. For example, the search system 120 may be provided with this information directly when a user, for example, indicates that Renner is an automobile manufacturer during a manual update of the classification information. In another example, search system 120 may detect entry of query phrases having, as constituent parts, the word "Renner" and other words or phrases that indicate a relationship between the word "Renner" and an automobile manufacturer (e.g., "car sales,"
"dealership," and "new car"). In this example, the search system 120 may glean the infonnation that "Renner" is an automobile manufacturer from context clues in other query phrases in the query stream. The search system 120 also includes manual classification process code segment 125 configured to classify a query phrase using a manual query classification technique. More particularly, code segment 125 may be configured to classify a query phrase based on a manually classified query phrase list, such as, for example, a list of query plirases that have previously been classified manually by a human, or third party, editor. For example, the query phrase "BMW wheels" may be classified as belonging to the automobile category because the query phrase "BMW wheels" was previously classified into the automobile category by a human editor. In some implementations, if a constituent part of the query phrase being classified was previously classified into a' category by a human editor, the entire query phrase may be associated with the category of the constituent part. For example, if the constituent part "BMW" was previously classified into the automobile category by a human editor, the query phrase "BMW
wheels" also may be associated with the automobile category.
The search system 120 also includes supervised machine learning classification process code segment 126 configured to classify a query phrase using a supervised machine learning query classification technique. In general, supervised machine learning involves producing a function, which is modified, refined or learned over time, to transform input data to preferred output data. For example, a process of supervised machine learning may map a feature vector to a set of classes (e.g., categories) based on the learned function. More particularly, code segment 126 may be configured to use distinguishing features to classify a given query phrase into a category. The distinguishing features may be developed by using a seed list of query phrases that have been classified into categories (e.g., a training set) to determine features that relate to the differences between categories and/or query phrases that belong to one category and not another. In other words, the seed list of categories may be used to determine features that distinguish one category from another.
To classify a query phrase, code segment 126 may be configured to access a data store that includes the distinguishing features. For example, code segment 126 may classify the query phrase "BMW wheels" into the automobile category because the query phrase "BMW wheels" includes features that are associated with the automobile category. Query phrases having features that are associated with the automobile category (e.g., features that distinguish query phrases belonging to the automobile category from query phrases belonging to a different category) may include words or phrases that relate to automobiles (e.g., "wheels," "detailing," "trunk," "transmission," "service station,"
"brakes," and even slang phrases such as "pimp my ride"), as well as proper names of automobile manufacturers (e.g., BMW) or particular automobile inodels (e.g., 325i).
Thus, other query phrases, such as, for example, "BMW detailing," "Renner service station," "transmission service station," and "VW engine," which include one or more of these features, may siniilarly be classified in the automobile category. The search system 120 also includes classification arbiter code segment 127 configured to determine a category for a query phrase when the query phrase is classified using more than one of the query classification techniques. More particularly, code segment 127 may be configured to determine a category for a query phrase when at least two of the selectional preference, manual and supervised machine learning query classification techniques are used by the search system 120 to determine a category for the query phrase and the query classification techniques disagree on the classification of the query phrase.
In some implementations, code segment 127, when executed, may be configured to classify a query phrase based on a voting scheme. The voting scheme may cause code segment 127 to classify the query phrase into a category determined by a majority of the classification techniques. For example, the selectional preference query classification technique and the supervised machine learning query classification technique may determine a category of automobile for the query phrase "BMW wheels," while the manual query classification techiiique determines a category of European consumer goods for the query phrase. TiZ this example, code segment 127 may classify the query phrase into the automobile category because a majority of the query classification teclmiques so classified.
In some iniplementations, code segment 127, when executed, may be configured to classify a query plirase based on a strength of a classification of the query phrase using a particular query classification technique and an overall classification metric of the particular query classification technique. A query classification technique may classify a query phrase and also provide an indication of strength related to the classification, which indicates the correlation of the query phrase to the classification and thus may be seen as an indicator of the likelihood of error. In addition, each query classification technique may be associated with a general, or overall, classification metric relating to the overall confidence level in the classifications made by the particular query classification technique. Code segment 127 may take into account the particular classification strength for the classification of a particular query phrase and the overall classification metric for the particular query classification technique used. For example, the selectional preference query classification technique may classify the query phrase "BMW
wheels"
into the automobile category and provide a classification strength of medium.
The selectional preference query classification technique may have an overall classification metric of high. The manual query classification technique may classify the query phrase into the European consumer goods category and may provide a classification strength of low witli an overall classification metric of low. In this case, code segment 127 may select automobile category for the query phrase because a classification strength of medium plus an overall classification metric of high (for the selectional preference query classification technique) outweighs a classification strength of low with an overall classification metric of low (for the manual query classification technique).
As described, the classification strength and overall classification metrics may operate as weights to enable comparison between competing classifications and/or other decision making related to classifications.
Altenzatively, code segment 127, wlien executed, maybe configured to classify a query phrase based on a combination of the voting scheme and belief of strength-overall classification metric techniques.
In some implementations, code segment 127 may be configured to associate a query phrase with more than one classification when the query classification techniques disagree on the classification of the query phrase. In the present example, code segment 127, when executed, may classify the query phrase "BMW wheels" into both the automobile category and the European consumer goods category.
Search system 120 also includes query phrase routing process code segment 128 configured to route, or otherwise send, a query phrase to one or more baclcend databases based on the classification of the query phrase. A backend database is a search resource and may include private databases, websites, bulletin boards, or a backend search engine.
More particularly, code segment 128 may be configured to receive a query phrase and a category associated with a query phrase and determine one or more backend databases related to the received category (e.g., having a category that is the same, or similar, to the category associated with the query phrase) by accessing a data store (not shown) that includes a list of backend databases and associated categories.
The determiuied backend databases may constitute a preferred list of backend databases that is a subset of all available backend databases. hi some implementations, code seginent 128 may select a further subset of the determined backend databases when, for example, some of the baclcend databases in the preferred list include redundant information.
Code segment 128 also may be configured to route the query phrase, or a reformatted version of the query phrase, to the determined subset of backend databases in order that the search system 120 may receive search results responsive to the query phrase. For exaniple, code seginent 128 may receive the query phrase "BMW
wheels"
and the associated automobile category. Code segment 128 may route the query phrase to a subset of baclcend databases that are also associated with the automobile category, such as, for example, a subset of backend databases that includes a Cars Only database.
In some cases, code segment 128 may reformat the query phrase before routing it to a particular backend database. Reforinatting a query phrase may allow for the subset of backend databases to provide searcli results that are more responsive to the query phrase because the query phrase has been translated to a form that is best understood by a backend database. For example, if the Cars Only database requests query phrases where the automobile manufacturer is labeled and other constituent parts are added with a plus (+) sign, code segment 128 may reformat the query phrase "BMW wheels" to be "manufacturer = BMW + wheels" before routing it to the Cars Only database. In this way, search system 120 may assist in achieving the best search results for the query phrase (e.g., search results that are most responsive to the information sought by a user who entered the query phrase). Data store 124b, as well as data that may be accessed by atiy of code segment 124-128, such as the manually classified query phrase list, the supervised machine learning query classification technique distinguishing features, the overall classification metrics, and the baclcend database-associated category list, may be stored in computer-readable medium and associated with code segment 124-128, respectively. The data may be stored in persistent or non-volatile storage, though this need not necessarily be so. For example, backend database-associated category list may be stored only in memory, such as random access memory, of the search system, because the list may change dynamically as backend databases are added, removed, or changed.
Referring to Fig. 2, an exemplary process 200 performs a search based on classification of a query phrase using a selectional preference query classification technique. Process 200 may be performed by a search system, such as search system 120 of Fig. 1.
Search system 120 receives a query phrase (step 210). The query phrase may be entered by a user seeking information related to the query phrase.
The search system 120 parses the query phrase into constituent parts (step 220).
As described above, a query phrase includes constituent parts and a constituent part may be an individual word, a smaller phrase of more than one word witliin the query phrase or the entire query phrase.
The search system 120 determines whether a relevant pattern of query phrases exists for the query phrase (step 230). The relevant pattern may be stored in classification information and created during the training of the selectional preference query classification technique, as described in detail below. Tii some implementations, a pattern may be a relevant pattern if the query phrase has a structure that is similar to the pattern. Additionally, or alternatively, a pattern may be a relevant pattern if the query phrase has one or more constituent parts that are the same as, or similar to, a constituent part in the pattern. Constituent parts may be similar if the constituent parts belong to the same category or have other common characteristics, such as, for example, having the same or similar definitional information. Definitional information may include a description of the constituent part. For example, the word "Ford" may have definitional information indicating that the word "Ford" relates to an automobile manufacturer.
The search system 120 determines a category associated with the relevant pattern (step 240). In some implementations, the relevant pattern may be associated with more than one category. For example, the pattern of automobile manufacturer plus the word "wheels" inay be associated with an automobile category a.nd a consumer goods category.
The search system 120 associates the query phrase with the category associated with the relevant pattern (step 250). In implementations where the pattern is associated with more than one category, the search system 120 may associate the query phrase with all, a subset, or a single one of the multiple categories associated with the relevant pattern.
The search system 120 routes the query phrase to a backend database based on the category associated with the query phrase (step 260). More particularly, the search system 120 may access a list of categories and related backend databases. The search system 120 may compare the category (or categories) associated with the query phrase to the categories in the list and identify backend databases that correspond to the matching categories. The search system 120 may route, or otherwise send, the query phrase to all, or a subset, of the identified backend databases. As described previously, a reformatted version of a query phrase may be sent to the identified backend databases instead of, or in addition to, the original query phrase in order to receive more responsive search results from the backend databases.
In some iinplementations, the query phrase may be sent to more than one backend database (e.g., a subset of all backend databases or a subset of a preferred list of backend databases) if more than one baclcend database is associated with a category that is the same as, or similar to, the category associated with the query phrase.
Furthermore, the query phrase may be sent to more than one backend database if the query phrase is associated with more than one. category.
The search system 120 receives search results from the backend database and enables presentation of the search results to the user (step 270). If the query phrase is sent to more than one backend database, the search system 120 may receive search results from each of the backend databases to which the query phrase (or a reformatted version of the query phrase) was sent.
In some implementations, the presentation of the search results may be altered based on the category related to the query phrase and backend database from which the search results are received. For example, a map may be presented in response to a geographic query phrase and/or an extracted list of comparison prices may be presented in response to a shopping query phrase. Search results received from an appropriate backend database, and optionally altered based on the classification of the query phrase, may be more responsive to a particular query plirase entered by a user seeking infonnation related to the particular query phrase.
In the manner described, a large portion of a general query stream (e.g., a stream of query phrases being entered by users and received by a search system) may be classified. Classification of the general query stream as a whole may allow tracking of trends over time. A search system may use trend tracking data as a mechanism for identifying areas that may require additional resources (e.g. additional hardware or new backend databases).
The search system 120 may optionally deterinine an advertisement related to the category associated with the query phrase and enable presentation of the advertisement to the user (step 280). If the query phrase is associated with more than one category, an advertisement related to one or more of the categories associated with the query phrase may be determined and presented to the user.
Referring to Fig. 3, a process 300 illustrates an example of performing a search based on classification of a query phrase using a selectional preference query classification technique. Block diagram 300 includes, iyater alia, query phrase 310, parser 320, classification information 330 including pattein 335, query phrase reformatting unit 340, backend databases 350 and user interface 360.
More particularly, query phrase 310 relates to the query phrase "BMW wheels."
Query phrase 310 may be entered by a user via a user interface (not shown).
Query phrase 310 may be sent to parser 320. Parser 320 may break down the query phrase 310 into its constituent parts. For example, query phrase 310 may be broken down into constituent parts 311, such as "BMW," "wheels" and "BMW wheels."
The constituent parts may be compared with classification information 330 to determine if a relevant pattern exists for query phrase 310. Classification information 330 includes pattern 335. Pattern 335 includes the pattern of automobile manufacturer plus the word "wheels" (abbreviated in the figure as "automobile maker +
wheels").
Query plirase 310 may be deemed similar to pattern 335 because query phrase 310 has at least one constituent part in common with pattern 335. Additionally, or alternatively, query phrase 310 also may be deemed similar to pattern 335 because query phrase 310 includes an automobile manufacturer (e.g., BMW) and the word "wheels." In other words, query phrase 310 fits witliin pattern 335. Pattern 335, therefore, is a relevant pattern for query phrase 310 and may be used to classify query phrase 310 into a category associated with the pattenz 335. Here, pattern 335 is associated with the automobile category, and thus, query phrase 310 also may be associated with the automobile category.
Based on the classification of query phrase 310 into the automobile category 312, the query phrase 310 may be reformatted by query plirase reformatting unit 340. For example, a category of automobile 312 may indicate that backend databases related to automobiles are most appropriate to be searched for the query phrase 310.
Furthermore, the automobile category 312 also may indicate that it is desirable to send a reformatted query phrase to the automobile backend databases. For example, backend databases related to automobiles may return better results if an automobile manufacturer in the query phrase is labeled and additional words are appended with a plus (+) symbol. Thus, query phrase reforn-iatting unit 340 may refomiat query phrase 310 into reformatted query phrase 312 "inanufacturer = BMW + wheels."
Category automobile 312 and reformatted query phrase 313 may be sent to backend databases 350. In some impleinentations, original query phrase 310 may be sent to backend databases 350 in addition to reformatted query phrase 313. In the configuration where it may not be helpful to send a reformatted query phrase to a backend database, the original query phrase 310 may be sent instead of reformatted query phrase 313.
Backend databases 350 include several baclcend databases related to particular categories. For example, backend database 350a is related to an automobile category.
Backend databases 350 also include advertisements database 350b, which includes advertisements related to particular categories. In some implementations, advertisements database 350b may include particular sub-databases having advertisements related to particular categories. For example, there may be an automobile advertisements database that includes advertisements related to the automobile category.
Each of backend databases 350, such as baclcend database 350a, may include more than one backend database related to automobiles, for example, such that backend database 350a includes a subset (e.g., a preferred list) of all available backend databases that are associated with automobiles. Furthermore, each of backend databases 350 also may include websites, search engines, and other search resources within the subset of backend databases.
Reformatted query phrase 313 may be sent to backend databases that have a category that is the saine as, or similar to, the category associated with the query phrase 313 (and reformatted query phrase 313). In this example, reformatted query phrase 313 is sent to backend database 350a, the automobiles backend database. Backend database 350a may be searched for search results that are responsive to the reformatted query phrase 313. In addition, advertisements database 350b also may be searched for advertisements related to the automobiles category.
Search results 314 may be received from autoniobiles backend database 350a and advertisement 315 may be received from advertisements database 350b. Search results 314 and advertisement 315 may be presented to the user who entered the query phrase 310 by displaying the query phrase 310, search results 314 and advertisement 315 in a user interface, such as user interface 360. In some implementations, user interface 360 may display the reformatted query phrase 313 in addition to, or instead of, original query phrase 310.Referring to Fig. 4, an exemplary process 400 trains a selectional preference query classification technique. Process 400 may be performed by a search system, such as search system 120 of Fig. 1.
The search system 120 receives a query phrase (step 410). The query phrase may be one of many query phrases in a set of query phrases received from a general query stream and stored to be used to train the selectional preference query classification technique.
The search system parses the query phrase into constituent parts (step 420).
The search system determines whether a constituent part is associated with a category (step 430). To do so, the search system may access a data store that includes constituent parts (e.g., words or phrases that make up larger query phrases) and associated categories. For example, the data store may include the constituent part "BMW" and one or more associated categories, such as "automobile," "European" and "consumer products." If a category has been associated with the constituent part, the search system 120 may associate the query phrase with the constituent part and the category associated with the constituent part (step 440). In some implementations, the query phrase also may be associated with the constituent part.
The search system 120 receives additional query phrases having a constituent part that is the same as, or similar to, a constituent part of the received query phrase (step 450). The additional query phrases also may be received from a set of query phrases received from the general query streain and stored. The search system 120 recognizes a pattern of query phrases having a same, or a similar, constituent part (step 460). A
constituent part may be similar to another constituent part if the constituent parts belong to the same (or a similar) category or have the same definitional information.
Based on the recognized pattern, the search system 120 associates the pattern of query phrases with the category associated with the coirunon constituent part (step 470).
The pattern and associated category may be used by the selectional preference query classification technique to classify later received query phrases, as described above.
Referring to Fig. 5, a process500 illustrates an example of training a selectional preference query classification technique for a particular pattern. Block diagram 500 includes query phrases 510, parser 520, selectional preference trainer 530 and classification information 540.
More particularly, query phrases 510 includes query phrases 510a "BMW
wheels," 510b "Nissan wheels," 510c "Kia wheels" and 510d "Ford wheels." Thus, each of query phrases 510a-510d includes an automobile manufacturer plus the word "wheels."
Each query phrase may be parsed into its constituent parts by parser 520 in a manner similar to that described with respect to parser 320 of Fig. 3. For example, query phrase 510a may be parsed into constituent phrases "BMW," "wheels," and "BMW
wheels."
The constituent parts for a particular query phrase may be provided to selectional preference trainer 530. Selectional preference trainer 530 includes query storage 523, constituent part-category database 534 and pattern finder 536. Query storage 523 may be configured to store query plirases that have been, or will be, used to detect a pattern. For example, query storage 523 includes the query phrases 510b, 510c, 510d and newly added query pllrase 510a BMW wheels.
Constituent part-category database 534 may be configured to store an association between a particular constituent part and a category to which the particular constituent part belongs. For example, the constituent part "wheels" belongs to the automobile category. In some implementations, constituent part-category database 534 also may store information related to a constituent part that is not necessarily a category, such as, for example, definitional information for the constituent part. Additionally, or alternatively, constituent part-category database may include category and/or definitional information for a particular constituent part.
Pattern finder 536 may be configured to detect patterns among a series of query phrases. For example, pattein finder 536 may detect a pattern among query phrases 510a-510d. More particularly, pattern finder 536 may detect a pattern of the form "automobile manufacturer + wheels" among query phrases 510a-510d. The pattern may be detected because query phrases 510a-510d have a constituent part in common (e.g., the word "wheels") and also include a similar constituent part (e.g., definitional information indicating that the constituent part relates to an automobile manufacturer).
However, one of these similarities between query phrases 510a-510d may be enougli for a pattern to be detected by pattern finder 536.
Pattern finder 536 also may associate the detected pattern with a category.
The category may be chosen based on a category of one or more of the constituent parts related to the detected pattern. In some implementations, pattern finder 536 may associate a pattern with all, or a subset of all, the categories associated with any query phrases that fit within the pattern. Additionally, pattern finder 536 also may associate a pattern and related category with particular constituent parts and definitional information.
This information may be used to determine if a particular query phrase falls within the pattern and thus, may be associated with one or more of the categories associated with the pattern.
The detected pattern and related infonnation may be stored in classification information 540. Classification information 540 may be used by the selectional preference query classification technique to determine if a relevant pattern exists for a particular query phrase. If so, classification information 540 may provide one or more categories associated with the relevant pattern to be associated with the query phrase.
The query phrase may be routed to one or more appropriate baclcend databases based on the category provided by classification information 540 in order to receive search results that are the most responsive to a user-entered query phrase.
Referring to Fig. 6, a process 600 illustrates an example of performing a search for a query phrase based on a classification of the query phrase using a combination of query classification techniques. More particularly, the query phrase may be associated with one or more categories based on a combination of query classification techniques.
Search results responsive to the query phrase may be received by searching for the query phrase in backend databases that are related to a category associated with the query phrase. Block diagram 600 includes query phrase 610, query classification techniques 622, 624 and 626, classification arbiter 630, category association unit 640, databases 650 and query search results 660.
Query phrase 610 may be entered by a user seeking information related to the query phrase. For example, a user may enter the query phrase "BMW wheels" to find information related to wheels for a car made by automobile inanufacturer BMW.
Query phrase 610 may be associated with a category by query classification techniques 620. More particularly, a manual query classification technique 622, a selectional preference query classification teclmique 624 and a supervised machine learning query classification technique 626 may each determine a category to be associated with query phrase 610.
Manual query classification technique 622 may deterrnine a category for query phrase 610 based on a manually classified query phrase list, such as, for exan.iple, a list of query phrases that were previously classified by a human editor). For example, the query phrase "BMW wheels" may be determined to belong to a category related to European consumer goods because the query phrase "BMW wheels," or a constituent part of the query plirase, such as, for example, "BMW," was previously manually classified into the European consumer goods category by a human editor.
Selectional preference query classification technique may determine a category for query phrase 610 in a manner similar to that described with respect to process 200 of Fig. 2. More particularly, if a relevant pattern exists for query phrase 610, a category (or several categories) associated with the relevant pattern may be determined for query phrase 610. For example, a pattern for automobile manufacturer plus the word "wheels"
may be a relevant pattern for the query phrase "BMW wheels." Thus, because the relevant pattern may be associated with an automobile category, the category automobile may be determined for the query phrase.
Supervised machine learning query classification technique 626 also may determine a category for query phrase 610. More particularly, supervised machine learning query classification technique may use distinguishing features to classify a given query phrase into a category. The distinguishing features may be developed by using a seed list of query phrases that have been classified into categories (e.g., a training set) to determine features that relate to the differences between categories and/or query phrases that belong to a particular category. In other words, the seed list of categories may be used to determine features that distinguish one category from another. For example, code segment 126 may classify the query phrase "BMW wheels" into the automobile category because the query phrase "BMW wheels" includes features that are associated with the automobile category, as described above with respect to Fig. 2.
There may be situations where one or more of query classification techniques 622, 624 and 626 may disagree on the classification of the query phrase.
Classification arbiter 630 may select among the possible categories determined by the query classification techniques 620 wlien the query classification techniques disagree on the classification of query phrase 610. Alternatively, classification arbiter 630 may select more than one classification for query phrase 610 when the query classification techniques are inconsistent, and thus, determine more than one classification for query phrase 610. In the present example, selectional preference query classification technique 624 and supervised machine learning query classif cation technique 626 may determine a category of automobile for query phrase 610, while manual query classification technique 622 may determine a category of European consumer goods for query phrase 610.
Mairy techniques may be used by classification arbiter 630 as described above with respect to Fig. 2. In the present example, based on the voting scheme technique, the classification arbiter 630 may select the automobile category for query phrase because two of the three query classification techniques determined the automobile category for the query phrase 610. The same result may arise when the classification arbiter 630 is configured based on the classification strength-overall classification metric technique. In this case, the classification arbiter 630 may select the automobile category for query phrase 610 because a classification strength of medium plus an overall classification metric of high (for the selectional preference query classification technique) outweighs a classification strength of low with an overall classification metric of low (for the manual query classification technique). The classification arbiter 630, when configured to classify query phrase 610 based on a combination of these two techniques, also may select the automobile category for query phrase 610. Alternatively, the classification arbiter 630 may classify query phrase 610 into both the automobile and European consumer goods categories.
The category (or categories) determined by classification arbiter 630 (or query classification techniques 622, 624 and 626 if no disagreement as to the classification is present) may be associated with query phrase 610 by category association unit 640. For example, category association unit 640 may associate the category automobile with the query phrase "BMW wheels."
In some implementations, the association between the query phrase 610 and the automobile category also may be stored and provided to a selectional preference training module, such as selectional preference trainer 530 of Fig. 5. The query phrase and associated category may be used (immediately or in the future) to update the classification infonnation and improve the classifications performed by the selectional preference query classification technique or the other query classification techniques.
Query phrase 610 may be routed to backend databases 650 to determine search results for query phrase 610. More particularly, query phrase 610 may be routed, or otherwise sent, to a subset of backend databases 655 based on the category associated with the query phrase. The subset of backend databases 655 include backend databases having at least one category in common with query phrase 610. For example, query phrase 610, being associated with the automobile category, may be routed to a Cars Only database, where the Cars Only database has a category of automobile. In another example, if query phrase 610 is associated with both the automobile and European consumer goods categories, the subset of baclcend databases 655 may include baclcend databases having a category of automobile (e.g., the Cars Only database), backend databases having a category of European consumer goods (e.g., a Buy Europe database), and baclcend databases having both categories (e.g., a New European Cars).
Search results 660 may be received from the subset of backend databases 655.
The search results are responsive to query phrase 610. Search results may include websites having information related to query phrase 610, advertisements and websites selling products related to query phrase 610, and web logs, news feeds, or bulletin boards including information responsive to query phrase 610. For example, search results 660 may include a website that is selling wheels for cars made by BMW direct from the manufacturer. The search results 660 may be presented to the user who entered query phrase 610.
In some implementations, the presentation of the search results may be altered based on the category related to the query phrase and backend database from which the search results are received. For example, a map may be presented in response to a geographic query phrase and/or an extracted list of comparison prices may be presented in response to a shopping query phrase. Search results received from an appropriate backend database, and optionally altered based on the classification of the query phrase, may be more responsive to a particular query plirase entered by a user seeking information related to the particular query phrase.
In some implementations, a category that has been associated with a query phrase by search system 120 may be presented to a user. The category may be presented to the user at the saine time as, or prior to, presentation and display of the search results. The search system 120 may be configured to receive input from the user as to the classification of the user's query phrase into a category in order to positively affect which backend databases the query phrase may be routed to and, ultimately, the search results provided for the query phrase. In some implementations, the search system 120 may be configured to allow a user to provide a category for the query phrase at the same time the user enters the query phrase. Alternatively, or additionally, the user may provide input before or after the category and/or search results are displayed to the user.
If the user provides input before search results are displayed, the search system 120 may take the user's input into account when routing the query phrase to one or more baclcend databases. If the input is provided by the user after search results are displayed, the search system 120 may re-route the query phrase to the backend databases and return search results that are more responsive to the user's request.
In one exainple, a user may enter the query phrase "eagles." The search system 120 may determine that two categories, such as, for example, football and birds, are associated with the query phrase. However, in many cases, the user is interested in one of these categories, but probably not both. Thus, if the search system 120 routes the query phrase "eagles" to backend databases having categories related to both football and birds, half of the search results retrieved and displayed to the user may not be responsive to the user's request.
In some implementations, the search system 120 may make an educated guess as to which category is responsive to the user's request and route the query phrase accordingly. In the present example, the search system 120 may guess that the user is interested in information about birds and not a football team. The search system 120 may provide the user with both the guessed category (e.g., birds) and the rejected category (e.g., football) and enable the user to indicate that the search system 120 guessed incorrectly (e.g., the user is interested in the football team, not birds).
Upon indicating that the search system 120 guessed incorrectly, the user may provide a correct category for the query phrase. The user may provide the correct category by selecting from one of the other categories presented (e.g., the rejected category) or inputting a different category. Based on the newly received category information, the search system 120 may re-route the query phrase and provide new search results accordingly.
The described systeins, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in coinbinations of these eleinents. Apparatus embodying these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process embodying these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output. The techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one progranunable processor coupled to receive data and instructions from, and to transinit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in asseinbly or machine language if desired; and in any case, the language may be a coinpiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks;
and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
It will be understood that various modifications may be made without departing from the spirit and scope of the claims. For example, useful results still could be achieved if steps of the disclosed techniques were performed in a different order and/or if components in the disclosed systems were combined in a different manner and/or replaced or supplemented by other components. Accordingly, other iinplementations are within the scope of the following claims.
Fig. 1 is a block diagram of a communications system capable of classifying a query phrase and routing the query phrase to a backend database related to the query phrase classification.
Fig. 2 is a flow chart of a process for performing a search based on classification of a query phrase using a selectional preference query classification teciznique.
Fig. 3 is a block diagranl illustrating an example of performing a search based on classification of a query plirase using a selectional preference query classification technique.
Fig. 4 is a flow chart of a process for training a selectional preference query classification technique.
Fig. 5 is a block diagram illustrating an example of training a selectional preference query classification technique for a particular pattern.
Fig. 6 is a block diagram illustrating an example of perforining a search for a query phrase based on a classification of the query phrase using a combination of query classification techniques.
Like reference synlbols in the various drawings indicate like elements.
DETAILED DESCRIPTION
Search engines, both for the Web and for enterprises, may automatically route an incoming query phrase to several specialized backend databases and may merge the search results received from those databases to create a merged listing. To receive meaningful search results, the inetasearch system selects a subset of all available backend databases, based, for instance, on the relative appropriateness of each database to the query phrase. Being selective with routing decisions may result in a relatively high ratio of relevant results, which results in more efficient and less costly processing when compared with results that follow from sending every query phrase to every backend database and the relatively low ratio of relevant results following therefrom.
Techniques are described for automatically classifying a query phrase among one or more topics of interest (e.g., categories) and using those topics of interest to assist in routing the query phrase to an appropriate subset of available backend databases. A
selectional preference query classification technique may be used to select a subset of backend databases (or other searchable resources or search processes) based on a coinparison between a query phrase and patterns of query phrases.
Additionally, or alternatively, a combination of query classification techniques may be used to classify a query phrase. Techniques also are described for using topical classification of a query phrase to assist a search system in delivering auxiliary information to a user who entered the query phrase. Advertisements, for instance, may be tailored based on classification rather than query keywords.
Referring to Fig. 1, a communications system 100 is configured to classify a query phrase and, based on the query phrase classification, route the query phrase to a backend database related to the query phrase classification. More particularly, the communications system 100 is configured to deliver and exchange messages between a client system 110 and a search system 120 through a delivery networlc 115 to classify a user entered query phrase into a topical category and provide search results received from a backend database to which the query phrase is routed and which is related to the query phrase classification.
Each of the client system 110 and the search system 120 may be a general-purpose computer (e.g., a personal computer, a desktop computer, or a laptop computer) configured to respond to and execute instructions in a defined manner. Other examples of the client system 110 and the search system 120 include a special-purpose computer, a workstation, a server, a device, a component, other physical or virtual equipment or some combination thereof capable of responding to and executing instructions. The client system 110 also may be a personal digital assistant (PDA), a communications device, such as a mobile telephone, or a mobile device that is a combination of a PDA
and communications device.
The client system 110 also includes a communication application 112 and is configured to use the communication application 112 to establish a conununication session with the search system 120 over the delivery network 115. The communication application 112 may be, for example, a browser or another type of communication application that is capable of accessing the search system 120. In another example, the communication application 112 may be a client-side application configured to communicate with the search system 120. The client system 110 is configured to send to the searcll system 120 requests for search results (e.g., a query phrase entered by a user).
The client system 110 also is configured to receive search results from the search system 120 and to present the received search results to the user.
The delivery networlc 115 provides a direct or indirect communication link between the client system 110 and the search system 120, irrespective of physical separation. Exainples of a delivery network 115 include the In.ternet, the World Wide Web, WANs, LANs, analog or digital wired and wireless telephone networks (e.g., PSTN
("Public Switched Telephone Network"), ISDN ("Integrated Services Digital Network"), and DSL ("Digital Subscriber Line") including various fonns of DSL such as SDSL
("Single-line Digital Subscriber Line"), ADSL ("Asymmetric Digital Subscriber Loop), HDSL ("High bit-rate Digital Subscriber Line"), and VDSL ("Very high bit-rate Digital Subscriber Line)), radio, television, cable, satellite, and/or any other delivery mechanism for carrying data.
The delivery network 115 includes communication pathways 117 that enable the client system 110 and the search system 120 to communicate with the delivery networlc 115. Each of the communication pathways 117 may include, for example, a wired, wireless, virtual, cable or satellite communications pathway.
The search system 120 may receive instructions from, for example, a software application, a program, a piece of code, a device, a coinputer, a computer system, or a combination thereof, which independently or collectively direct steps, as described herein. The search system 120 includes a communication application 122 that is configured to enable the search system 120 to communicate with the client system 110 through the delivery network 115.
The search system 120 may be a host system, such as an Internet service provider that provides a search service to subscribers. In another example, the search system 120 may be a system that hosts a web site that provides search services to the general public.
The search system 120 also may be referred to as a search engine or a search service.
In general, the search system 120 may be configured to classify a user entered query phrase into a topical category and provide search results received from a backend database to which the query pllrase is routed and which is related to the query phrase classification.
More particularly, the search system 120 includes selectional preference unit configured to classify a query phrase. Selectional preference unit 124 includes classification process code segment 124a, classification information data store 124b and training process code segment 124c.
Classification process code segment 124a may be configured to receive a query phrase entered by a user at client 110. For example, code segment 124a may receive the query phrase "BMW wheels." Code segment 124a may be further configured to detennine and associate a category with the received query phrase. To do so, code segment 124a may access classification information data store 124b.
Classification information data store 124b may be configured to store information related to patterns of query phrases and associated categories. A query phrase may include constituent parts, where a constituent part may be an individual word, a smaller phrase of more than one word within the query phrase or the entire query phrase. Data store 124b may be configured to store a category associated with a particular pattern of query phrases having the same, or similar, constituent parts. In some implementations, data store 124b may be configured to store an association between a category, or some other descriptive or definitional infonnation, and a particular individual constituent part.
For example, data store 124b may store a pattern of query phrases that include a particular automobile manufacturer plus the word "wheels." The pattern may be associated with the category "automobile." Furthermore, in some impleinentations, the constituent part "wheels" also may be associated with the automobile category.
Training process code segment 124c may be configured to detect a pattern of query phrases, associate a detected pattern with a category and store the detected pattern and associated category information in data store 124b, as described in detail below.
Code segment 124c may be executed for the purpose of setting up initial classification infornaation to be used by code segment 124a to classify a query phrase. For example, in keeping with the above noted example used with respect to data store 124b, code segment 124c may be executed to detect a pattern of query phrases that include an automobile manufacturer plus the word "wheels" based on a series of query phrases, such as Ford plus wheels or Nissan plus wheels.
In some implementations, code segment 124c may be configured to determine whether a relationship between a detected pattern and a category is strong enougli to warrant associating the detected pattern with the category and storing the information in data store 124b for use in categorizing future query phrases. If the strength of the relationsllip satisfies a threshold, the detected patteni and associated category may be useful in categorizing future query phrases and will be stored in data store 124b. If the strength of the relationship does not satisfy the threshold, the detected pattern may not be useful in categorizing future query phrases. In this example, the detected pattern may not be associated with the category, nor stored in data store 124b for future use.
Alternatively or additionally, if a different category exists with which the detected pattern may be associated, code segment 124c may associate the detected pattern with the different category, and store the information in data store 124b, if there is a stronger (and more useful) relationship between the detected pattern and the different category.
Code segment 124c also may be executed at predetermined intervals, or upon the happening of a particular event (e.g., a user request) to update the classification information stored in data store 124b. For example, a new automobile manufacturer may come into the market, such as Renner Automotive. In this example, code segment 124c may be executed to update the classification information within data store 124b to include Renner plus the word "wheels" in the detected pattern of automobile manufacturer plus the word "wheels" because "Renner" is an automobile manufacturer.
Furthermore, code segment 124c may be configured to associate the new entry with the automobile category that is associated with the detected pattern. In some iinplementations, code segment 124c may be configured to associate the word "Renner"
with the automobile category and/or definitional information, such as, for example, to indicate that the word "Renner" refers to an automobile manufacturer.
The search system 120 may determine that Renner is an automobile manufacturer in several ways. For example, the search system 120 may be provided with this information directly when a user, for example, indicates that Renner is an automobile manufacturer during a manual update of the classification information. In another example, search system 120 may detect entry of query phrases having, as constituent parts, the word "Renner" and other words or phrases that indicate a relationship between the word "Renner" and an automobile manufacturer (e.g., "car sales,"
"dealership," and "new car"). In this example, the search system 120 may glean the infonnation that "Renner" is an automobile manufacturer from context clues in other query phrases in the query stream. The search system 120 also includes manual classification process code segment 125 configured to classify a query phrase using a manual query classification technique. More particularly, code segment 125 may be configured to classify a query phrase based on a manually classified query phrase list, such as, for example, a list of query plirases that have previously been classified manually by a human, or third party, editor. For example, the query phrase "BMW wheels" may be classified as belonging to the automobile category because the query phrase "BMW wheels" was previously classified into the automobile category by a human editor. In some implementations, if a constituent part of the query phrase being classified was previously classified into a' category by a human editor, the entire query phrase may be associated with the category of the constituent part. For example, if the constituent part "BMW" was previously classified into the automobile category by a human editor, the query phrase "BMW
wheels" also may be associated with the automobile category.
The search system 120 also includes supervised machine learning classification process code segment 126 configured to classify a query phrase using a supervised machine learning query classification technique. In general, supervised machine learning involves producing a function, which is modified, refined or learned over time, to transform input data to preferred output data. For example, a process of supervised machine learning may map a feature vector to a set of classes (e.g., categories) based on the learned function. More particularly, code segment 126 may be configured to use distinguishing features to classify a given query phrase into a category. The distinguishing features may be developed by using a seed list of query phrases that have been classified into categories (e.g., a training set) to determine features that relate to the differences between categories and/or query phrases that belong to one category and not another. In other words, the seed list of categories may be used to determine features that distinguish one category from another.
To classify a query phrase, code segment 126 may be configured to access a data store that includes the distinguishing features. For example, code segment 126 may classify the query phrase "BMW wheels" into the automobile category because the query phrase "BMW wheels" includes features that are associated with the automobile category. Query phrases having features that are associated with the automobile category (e.g., features that distinguish query phrases belonging to the automobile category from query phrases belonging to a different category) may include words or phrases that relate to automobiles (e.g., "wheels," "detailing," "trunk," "transmission," "service station,"
"brakes," and even slang phrases such as "pimp my ride"), as well as proper names of automobile manufacturers (e.g., BMW) or particular automobile inodels (e.g., 325i).
Thus, other query phrases, such as, for example, "BMW detailing," "Renner service station," "transmission service station," and "VW engine," which include one or more of these features, may siniilarly be classified in the automobile category. The search system 120 also includes classification arbiter code segment 127 configured to determine a category for a query phrase when the query phrase is classified using more than one of the query classification techniques. More particularly, code segment 127 may be configured to determine a category for a query phrase when at least two of the selectional preference, manual and supervised machine learning query classification techniques are used by the search system 120 to determine a category for the query phrase and the query classification techniques disagree on the classification of the query phrase.
In some implementations, code segment 127, when executed, may be configured to classify a query phrase based on a voting scheme. The voting scheme may cause code segment 127 to classify the query phrase into a category determined by a majority of the classification techniques. For example, the selectional preference query classification technique and the supervised machine learning query classification technique may determine a category of automobile for the query phrase "BMW wheels," while the manual query classification techiiique determines a category of European consumer goods for the query phrase. TiZ this example, code segment 127 may classify the query phrase into the automobile category because a majority of the query classification teclmiques so classified.
In some iniplementations, code segment 127, when executed, may be configured to classify a query plirase based on a strength of a classification of the query phrase using a particular query classification technique and an overall classification metric of the particular query classification technique. A query classification technique may classify a query phrase and also provide an indication of strength related to the classification, which indicates the correlation of the query phrase to the classification and thus may be seen as an indicator of the likelihood of error. In addition, each query classification technique may be associated with a general, or overall, classification metric relating to the overall confidence level in the classifications made by the particular query classification technique. Code segment 127 may take into account the particular classification strength for the classification of a particular query phrase and the overall classification metric for the particular query classification technique used. For example, the selectional preference query classification technique may classify the query phrase "BMW
wheels"
into the automobile category and provide a classification strength of medium.
The selectional preference query classification technique may have an overall classification metric of high. The manual query classification technique may classify the query phrase into the European consumer goods category and may provide a classification strength of low witli an overall classification metric of low. In this case, code segment 127 may select automobile category for the query phrase because a classification strength of medium plus an overall classification metric of high (for the selectional preference query classification technique) outweighs a classification strength of low with an overall classification metric of low (for the manual query classification technique).
As described, the classification strength and overall classification metrics may operate as weights to enable comparison between competing classifications and/or other decision making related to classifications.
Altenzatively, code segment 127, wlien executed, maybe configured to classify a query phrase based on a combination of the voting scheme and belief of strength-overall classification metric techniques.
In some implementations, code segment 127 may be configured to associate a query phrase with more than one classification when the query classification techniques disagree on the classification of the query phrase. In the present example, code segment 127, when executed, may classify the query phrase "BMW wheels" into both the automobile category and the European consumer goods category.
Search system 120 also includes query phrase routing process code segment 128 configured to route, or otherwise send, a query phrase to one or more baclcend databases based on the classification of the query phrase. A backend database is a search resource and may include private databases, websites, bulletin boards, or a backend search engine.
More particularly, code segment 128 may be configured to receive a query phrase and a category associated with a query phrase and determine one or more backend databases related to the received category (e.g., having a category that is the same, or similar, to the category associated with the query phrase) by accessing a data store (not shown) that includes a list of backend databases and associated categories.
The determiuied backend databases may constitute a preferred list of backend databases that is a subset of all available backend databases. hi some implementations, code seginent 128 may select a further subset of the determined backend databases when, for example, some of the baclcend databases in the preferred list include redundant information.
Code segment 128 also may be configured to route the query phrase, or a reformatted version of the query phrase, to the determined subset of backend databases in order that the search system 120 may receive search results responsive to the query phrase. For exaniple, code seginent 128 may receive the query phrase "BMW
wheels"
and the associated automobile category. Code segment 128 may route the query phrase to a subset of baclcend databases that are also associated with the automobile category, such as, for example, a subset of backend databases that includes a Cars Only database.
In some cases, code segment 128 may reformat the query phrase before routing it to a particular backend database. Reforinatting a query phrase may allow for the subset of backend databases to provide searcli results that are more responsive to the query phrase because the query phrase has been translated to a form that is best understood by a backend database. For example, if the Cars Only database requests query phrases where the automobile manufacturer is labeled and other constituent parts are added with a plus (+) sign, code segment 128 may reformat the query phrase "BMW wheels" to be "manufacturer = BMW + wheels" before routing it to the Cars Only database. In this way, search system 120 may assist in achieving the best search results for the query phrase (e.g., search results that are most responsive to the information sought by a user who entered the query phrase). Data store 124b, as well as data that may be accessed by atiy of code segment 124-128, such as the manually classified query phrase list, the supervised machine learning query classification technique distinguishing features, the overall classification metrics, and the baclcend database-associated category list, may be stored in computer-readable medium and associated with code segment 124-128, respectively. The data may be stored in persistent or non-volatile storage, though this need not necessarily be so. For example, backend database-associated category list may be stored only in memory, such as random access memory, of the search system, because the list may change dynamically as backend databases are added, removed, or changed.
Referring to Fig. 2, an exemplary process 200 performs a search based on classification of a query phrase using a selectional preference query classification technique. Process 200 may be performed by a search system, such as search system 120 of Fig. 1.
Search system 120 receives a query phrase (step 210). The query phrase may be entered by a user seeking information related to the query phrase.
The search system 120 parses the query phrase into constituent parts (step 220).
As described above, a query phrase includes constituent parts and a constituent part may be an individual word, a smaller phrase of more than one word witliin the query phrase or the entire query phrase.
The search system 120 determines whether a relevant pattern of query phrases exists for the query phrase (step 230). The relevant pattern may be stored in classification information and created during the training of the selectional preference query classification technique, as described in detail below. Tii some implementations, a pattern may be a relevant pattern if the query phrase has a structure that is similar to the pattern. Additionally, or alternatively, a pattern may be a relevant pattern if the query phrase has one or more constituent parts that are the same as, or similar to, a constituent part in the pattern. Constituent parts may be similar if the constituent parts belong to the same category or have other common characteristics, such as, for example, having the same or similar definitional information. Definitional information may include a description of the constituent part. For example, the word "Ford" may have definitional information indicating that the word "Ford" relates to an automobile manufacturer.
The search system 120 determines a category associated with the relevant pattern (step 240). In some implementations, the relevant pattern may be associated with more than one category. For example, the pattern of automobile manufacturer plus the word "wheels" inay be associated with an automobile category a.nd a consumer goods category.
The search system 120 associates the query phrase with the category associated with the relevant pattern (step 250). In implementations where the pattern is associated with more than one category, the search system 120 may associate the query phrase with all, a subset, or a single one of the multiple categories associated with the relevant pattern.
The search system 120 routes the query phrase to a backend database based on the category associated with the query phrase (step 260). More particularly, the search system 120 may access a list of categories and related backend databases. The search system 120 may compare the category (or categories) associated with the query phrase to the categories in the list and identify backend databases that correspond to the matching categories. The search system 120 may route, or otherwise send, the query phrase to all, or a subset, of the identified backend databases. As described previously, a reformatted version of a query phrase may be sent to the identified backend databases instead of, or in addition to, the original query phrase in order to receive more responsive search results from the backend databases.
In some iinplementations, the query phrase may be sent to more than one backend database (e.g., a subset of all backend databases or a subset of a preferred list of backend databases) if more than one baclcend database is associated with a category that is the same as, or similar to, the category associated with the query phrase.
Furthermore, the query phrase may be sent to more than one backend database if the query phrase is associated with more than one. category.
The search system 120 receives search results from the backend database and enables presentation of the search results to the user (step 270). If the query phrase is sent to more than one backend database, the search system 120 may receive search results from each of the backend databases to which the query phrase (or a reformatted version of the query phrase) was sent.
In some implementations, the presentation of the search results may be altered based on the category related to the query phrase and backend database from which the search results are received. For example, a map may be presented in response to a geographic query phrase and/or an extracted list of comparison prices may be presented in response to a shopping query phrase. Search results received from an appropriate backend database, and optionally altered based on the classification of the query phrase, may be more responsive to a particular query plirase entered by a user seeking infonnation related to the particular query phrase.
In the manner described, a large portion of a general query stream (e.g., a stream of query phrases being entered by users and received by a search system) may be classified. Classification of the general query stream as a whole may allow tracking of trends over time. A search system may use trend tracking data as a mechanism for identifying areas that may require additional resources (e.g. additional hardware or new backend databases).
The search system 120 may optionally deterinine an advertisement related to the category associated with the query phrase and enable presentation of the advertisement to the user (step 280). If the query phrase is associated with more than one category, an advertisement related to one or more of the categories associated with the query phrase may be determined and presented to the user.
Referring to Fig. 3, a process 300 illustrates an example of performing a search based on classification of a query phrase using a selectional preference query classification technique. Block diagram 300 includes, iyater alia, query phrase 310, parser 320, classification information 330 including pattein 335, query phrase reformatting unit 340, backend databases 350 and user interface 360.
More particularly, query phrase 310 relates to the query phrase "BMW wheels."
Query phrase 310 may be entered by a user via a user interface (not shown).
Query phrase 310 may be sent to parser 320. Parser 320 may break down the query phrase 310 into its constituent parts. For example, query phrase 310 may be broken down into constituent parts 311, such as "BMW," "wheels" and "BMW wheels."
The constituent parts may be compared with classification information 330 to determine if a relevant pattern exists for query phrase 310. Classification information 330 includes pattern 335. Pattern 335 includes the pattern of automobile manufacturer plus the word "wheels" (abbreviated in the figure as "automobile maker +
wheels").
Query plirase 310 may be deemed similar to pattern 335 because query phrase 310 has at least one constituent part in common with pattern 335. Additionally, or alternatively, query phrase 310 also may be deemed similar to pattern 335 because query phrase 310 includes an automobile manufacturer (e.g., BMW) and the word "wheels." In other words, query phrase 310 fits witliin pattern 335. Pattern 335, therefore, is a relevant pattern for query phrase 310 and may be used to classify query phrase 310 into a category associated with the pattenz 335. Here, pattern 335 is associated with the automobile category, and thus, query phrase 310 also may be associated with the automobile category.
Based on the classification of query phrase 310 into the automobile category 312, the query phrase 310 may be reformatted by query plirase reformatting unit 340. For example, a category of automobile 312 may indicate that backend databases related to automobiles are most appropriate to be searched for the query phrase 310.
Furthermore, the automobile category 312 also may indicate that it is desirable to send a reformatted query phrase to the automobile backend databases. For example, backend databases related to automobiles may return better results if an automobile manufacturer in the query phrase is labeled and additional words are appended with a plus (+) symbol. Thus, query phrase reforn-iatting unit 340 may refomiat query phrase 310 into reformatted query phrase 312 "inanufacturer = BMW + wheels."
Category automobile 312 and reformatted query phrase 313 may be sent to backend databases 350. In some impleinentations, original query phrase 310 may be sent to backend databases 350 in addition to reformatted query phrase 313. In the configuration where it may not be helpful to send a reformatted query phrase to a backend database, the original query phrase 310 may be sent instead of reformatted query phrase 313.
Backend databases 350 include several baclcend databases related to particular categories. For example, backend database 350a is related to an automobile category.
Backend databases 350 also include advertisements database 350b, which includes advertisements related to particular categories. In some implementations, advertisements database 350b may include particular sub-databases having advertisements related to particular categories. For example, there may be an automobile advertisements database that includes advertisements related to the automobile category.
Each of backend databases 350, such as baclcend database 350a, may include more than one backend database related to automobiles, for example, such that backend database 350a includes a subset (e.g., a preferred list) of all available backend databases that are associated with automobiles. Furthermore, each of backend databases 350 also may include websites, search engines, and other search resources within the subset of backend databases.
Reformatted query phrase 313 may be sent to backend databases that have a category that is the saine as, or similar to, the category associated with the query phrase 313 (and reformatted query phrase 313). In this example, reformatted query phrase 313 is sent to backend database 350a, the automobiles backend database. Backend database 350a may be searched for search results that are responsive to the reformatted query phrase 313. In addition, advertisements database 350b also may be searched for advertisements related to the automobiles category.
Search results 314 may be received from autoniobiles backend database 350a and advertisement 315 may be received from advertisements database 350b. Search results 314 and advertisement 315 may be presented to the user who entered the query phrase 310 by displaying the query phrase 310, search results 314 and advertisement 315 in a user interface, such as user interface 360. In some implementations, user interface 360 may display the reformatted query phrase 313 in addition to, or instead of, original query phrase 310.Referring to Fig. 4, an exemplary process 400 trains a selectional preference query classification technique. Process 400 may be performed by a search system, such as search system 120 of Fig. 1.
The search system 120 receives a query phrase (step 410). The query phrase may be one of many query phrases in a set of query phrases received from a general query stream and stored to be used to train the selectional preference query classification technique.
The search system parses the query phrase into constituent parts (step 420).
The search system determines whether a constituent part is associated with a category (step 430). To do so, the search system may access a data store that includes constituent parts (e.g., words or phrases that make up larger query phrases) and associated categories. For example, the data store may include the constituent part "BMW" and one or more associated categories, such as "automobile," "European" and "consumer products." If a category has been associated with the constituent part, the search system 120 may associate the query phrase with the constituent part and the category associated with the constituent part (step 440). In some implementations, the query phrase also may be associated with the constituent part.
The search system 120 receives additional query phrases having a constituent part that is the same as, or similar to, a constituent part of the received query phrase (step 450). The additional query phrases also may be received from a set of query phrases received from the general query streain and stored. The search system 120 recognizes a pattern of query phrases having a same, or a similar, constituent part (step 460). A
constituent part may be similar to another constituent part if the constituent parts belong to the same (or a similar) category or have the same definitional information.
Based on the recognized pattern, the search system 120 associates the pattern of query phrases with the category associated with the coirunon constituent part (step 470).
The pattern and associated category may be used by the selectional preference query classification technique to classify later received query phrases, as described above.
Referring to Fig. 5, a process500 illustrates an example of training a selectional preference query classification technique for a particular pattern. Block diagram 500 includes query phrases 510, parser 520, selectional preference trainer 530 and classification information 540.
More particularly, query phrases 510 includes query phrases 510a "BMW
wheels," 510b "Nissan wheels," 510c "Kia wheels" and 510d "Ford wheels." Thus, each of query phrases 510a-510d includes an automobile manufacturer plus the word "wheels."
Each query phrase may be parsed into its constituent parts by parser 520 in a manner similar to that described with respect to parser 320 of Fig. 3. For example, query phrase 510a may be parsed into constituent phrases "BMW," "wheels," and "BMW
wheels."
The constituent parts for a particular query phrase may be provided to selectional preference trainer 530. Selectional preference trainer 530 includes query storage 523, constituent part-category database 534 and pattern finder 536. Query storage 523 may be configured to store query plirases that have been, or will be, used to detect a pattern. For example, query storage 523 includes the query phrases 510b, 510c, 510d and newly added query pllrase 510a BMW wheels.
Constituent part-category database 534 may be configured to store an association between a particular constituent part and a category to which the particular constituent part belongs. For example, the constituent part "wheels" belongs to the automobile category. In some implementations, constituent part-category database 534 also may store information related to a constituent part that is not necessarily a category, such as, for example, definitional information for the constituent part. Additionally, or alternatively, constituent part-category database may include category and/or definitional information for a particular constituent part.
Pattern finder 536 may be configured to detect patterns among a series of query phrases. For example, pattein finder 536 may detect a pattern among query phrases 510a-510d. More particularly, pattern finder 536 may detect a pattern of the form "automobile manufacturer + wheels" among query phrases 510a-510d. The pattern may be detected because query phrases 510a-510d have a constituent part in common (e.g., the word "wheels") and also include a similar constituent part (e.g., definitional information indicating that the constituent part relates to an automobile manufacturer).
However, one of these similarities between query phrases 510a-510d may be enougli for a pattern to be detected by pattern finder 536.
Pattern finder 536 also may associate the detected pattern with a category.
The category may be chosen based on a category of one or more of the constituent parts related to the detected pattern. In some implementations, pattern finder 536 may associate a pattern with all, or a subset of all, the categories associated with any query phrases that fit within the pattern. Additionally, pattern finder 536 also may associate a pattern and related category with particular constituent parts and definitional information.
This information may be used to determine if a particular query phrase falls within the pattern and thus, may be associated with one or more of the categories associated with the pattern.
The detected pattern and related infonnation may be stored in classification information 540. Classification information 540 may be used by the selectional preference query classification technique to determine if a relevant pattern exists for a particular query phrase. If so, classification information 540 may provide one or more categories associated with the relevant pattern to be associated with the query phrase.
The query phrase may be routed to one or more appropriate baclcend databases based on the category provided by classification information 540 in order to receive search results that are the most responsive to a user-entered query phrase.
Referring to Fig. 6, a process 600 illustrates an example of performing a search for a query phrase based on a classification of the query phrase using a combination of query classification techniques. More particularly, the query phrase may be associated with one or more categories based on a combination of query classification techniques.
Search results responsive to the query phrase may be received by searching for the query phrase in backend databases that are related to a category associated with the query phrase. Block diagram 600 includes query phrase 610, query classification techniques 622, 624 and 626, classification arbiter 630, category association unit 640, databases 650 and query search results 660.
Query phrase 610 may be entered by a user seeking information related to the query phrase. For example, a user may enter the query phrase "BMW wheels" to find information related to wheels for a car made by automobile inanufacturer BMW.
Query phrase 610 may be associated with a category by query classification techniques 620. More particularly, a manual query classification technique 622, a selectional preference query classification teclmique 624 and a supervised machine learning query classification technique 626 may each determine a category to be associated with query phrase 610.
Manual query classification technique 622 may deterrnine a category for query phrase 610 based on a manually classified query phrase list, such as, for exan.iple, a list of query phrases that were previously classified by a human editor). For example, the query phrase "BMW wheels" may be determined to belong to a category related to European consumer goods because the query phrase "BMW wheels," or a constituent part of the query plirase, such as, for example, "BMW," was previously manually classified into the European consumer goods category by a human editor.
Selectional preference query classification technique may determine a category for query phrase 610 in a manner similar to that described with respect to process 200 of Fig. 2. More particularly, if a relevant pattern exists for query phrase 610, a category (or several categories) associated with the relevant pattern may be determined for query phrase 610. For example, a pattern for automobile manufacturer plus the word "wheels"
may be a relevant pattern for the query phrase "BMW wheels." Thus, because the relevant pattern may be associated with an automobile category, the category automobile may be determined for the query phrase.
Supervised machine learning query classification technique 626 also may determine a category for query phrase 610. More particularly, supervised machine learning query classification technique may use distinguishing features to classify a given query phrase into a category. The distinguishing features may be developed by using a seed list of query phrases that have been classified into categories (e.g., a training set) to determine features that relate to the differences between categories and/or query phrases that belong to a particular category. In other words, the seed list of categories may be used to determine features that distinguish one category from another. For example, code segment 126 may classify the query phrase "BMW wheels" into the automobile category because the query phrase "BMW wheels" includes features that are associated with the automobile category, as described above with respect to Fig. 2.
There may be situations where one or more of query classification techniques 622, 624 and 626 may disagree on the classification of the query phrase.
Classification arbiter 630 may select among the possible categories determined by the query classification techniques 620 wlien the query classification techniques disagree on the classification of query phrase 610. Alternatively, classification arbiter 630 may select more than one classification for query phrase 610 when the query classification techniques are inconsistent, and thus, determine more than one classification for query phrase 610. In the present example, selectional preference query classification technique 624 and supervised machine learning query classif cation technique 626 may determine a category of automobile for query phrase 610, while manual query classification technique 622 may determine a category of European consumer goods for query phrase 610.
Mairy techniques may be used by classification arbiter 630 as described above with respect to Fig. 2. In the present example, based on the voting scheme technique, the classification arbiter 630 may select the automobile category for query phrase because two of the three query classification techniques determined the automobile category for the query phrase 610. The same result may arise when the classification arbiter 630 is configured based on the classification strength-overall classification metric technique. In this case, the classification arbiter 630 may select the automobile category for query phrase 610 because a classification strength of medium plus an overall classification metric of high (for the selectional preference query classification technique) outweighs a classification strength of low with an overall classification metric of low (for the manual query classification technique). The classification arbiter 630, when configured to classify query phrase 610 based on a combination of these two techniques, also may select the automobile category for query phrase 610. Alternatively, the classification arbiter 630 may classify query phrase 610 into both the automobile and European consumer goods categories.
The category (or categories) determined by classification arbiter 630 (or query classification techniques 622, 624 and 626 if no disagreement as to the classification is present) may be associated with query phrase 610 by category association unit 640. For example, category association unit 640 may associate the category automobile with the query phrase "BMW wheels."
In some implementations, the association between the query phrase 610 and the automobile category also may be stored and provided to a selectional preference training module, such as selectional preference trainer 530 of Fig. 5. The query phrase and associated category may be used (immediately or in the future) to update the classification infonnation and improve the classifications performed by the selectional preference query classification technique or the other query classification techniques.
Query phrase 610 may be routed to backend databases 650 to determine search results for query phrase 610. More particularly, query phrase 610 may be routed, or otherwise sent, to a subset of backend databases 655 based on the category associated with the query phrase. The subset of backend databases 655 include backend databases having at least one category in common with query phrase 610. For example, query phrase 610, being associated with the automobile category, may be routed to a Cars Only database, where the Cars Only database has a category of automobile. In another example, if query phrase 610 is associated with both the automobile and European consumer goods categories, the subset of baclcend databases 655 may include baclcend databases having a category of automobile (e.g., the Cars Only database), backend databases having a category of European consumer goods (e.g., a Buy Europe database), and baclcend databases having both categories (e.g., a New European Cars).
Search results 660 may be received from the subset of backend databases 655.
The search results are responsive to query phrase 610. Search results may include websites having information related to query phrase 610, advertisements and websites selling products related to query phrase 610, and web logs, news feeds, or bulletin boards including information responsive to query phrase 610. For example, search results 660 may include a website that is selling wheels for cars made by BMW direct from the manufacturer. The search results 660 may be presented to the user who entered query phrase 610.
In some implementations, the presentation of the search results may be altered based on the category related to the query phrase and backend database from which the search results are received. For example, a map may be presented in response to a geographic query phrase and/or an extracted list of comparison prices may be presented in response to a shopping query phrase. Search results received from an appropriate backend database, and optionally altered based on the classification of the query phrase, may be more responsive to a particular query plirase entered by a user seeking information related to the particular query phrase.
In some implementations, a category that has been associated with a query phrase by search system 120 may be presented to a user. The category may be presented to the user at the saine time as, or prior to, presentation and display of the search results. The search system 120 may be configured to receive input from the user as to the classification of the user's query phrase into a category in order to positively affect which backend databases the query phrase may be routed to and, ultimately, the search results provided for the query phrase. In some implementations, the search system 120 may be configured to allow a user to provide a category for the query phrase at the same time the user enters the query phrase. Alternatively, or additionally, the user may provide input before or after the category and/or search results are displayed to the user.
If the user provides input before search results are displayed, the search system 120 may take the user's input into account when routing the query phrase to one or more baclcend databases. If the input is provided by the user after search results are displayed, the search system 120 may re-route the query phrase to the backend databases and return search results that are more responsive to the user's request.
In one exainple, a user may enter the query phrase "eagles." The search system 120 may determine that two categories, such as, for example, football and birds, are associated with the query phrase. However, in many cases, the user is interested in one of these categories, but probably not both. Thus, if the search system 120 routes the query phrase "eagles" to backend databases having categories related to both football and birds, half of the search results retrieved and displayed to the user may not be responsive to the user's request.
In some implementations, the search system 120 may make an educated guess as to which category is responsive to the user's request and route the query phrase accordingly. In the present example, the search system 120 may guess that the user is interested in information about birds and not a football team. The search system 120 may provide the user with both the guessed category (e.g., birds) and the rejected category (e.g., football) and enable the user to indicate that the search system 120 guessed incorrectly (e.g., the user is interested in the football team, not birds).
Upon indicating that the search system 120 guessed incorrectly, the user may provide a correct category for the query phrase. The user may provide the correct category by selecting from one of the other categories presented (e.g., the rejected category) or inputting a different category. Based on the newly received category information, the search system 120 may re-route the query phrase and provide new search results accordingly.
The described systeins, methods, and techniques may be implemented in digital electronic circuitry, computer hardware, firmware, software, or in coinbinations of these eleinents. Apparatus embodying these techniques may include appropriate input and output devices, a computer processor, and a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor. A process embodying these techniques may be performed by a programmable processor executing a program of instructions to perform desired functions by operating on input data and generating appropriate output. The techniques may be implemented in one or more computer programs that are executable on a programmable system including at least one progranunable processor coupled to receive data and instructions from, and to transinit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in asseinbly or machine language if desired; and in any case, the language may be a coinpiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks;
and Compact Disc Read-Only Memory (CD-ROM). Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
It will be understood that various modifications may be made without departing from the spirit and scope of the claims. For example, useful results still could be achieved if steps of the disclosed techniques were performed in a different order and/or if components in the disclosed systems were combined in a different manner and/or replaced or supplemented by other components. Accordingly, other iinplementations are within the scope of the following claims.
Claims (29)
1. A method, performed at least partially on a computer, for enabling satisfaction of a search responsive to a query based on classification of the query, the method comprising:
receiving, from user input, a query phrase;
parsing the received query phrase into constituent parts;
accessing, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
determining whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern, associating the category that is associated with the pattern also with the query phrase or the constituent part; and identifying at least one search resource for satisfying the query phrase based on the associated category.
receiving, from user input, a query phrase;
parsing the received query phrase into constituent parts;
accessing, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
determining whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern, associating the category that is associated with the pattern also with the query phrase or the constituent part; and identifying at least one search resource for satisfying the query phrase based on the associated category.
2. The method of claim 1 further comprising enabling routing of the query phrase to the at least one identified search resource.
3. The method of claim 1 wherein associating the category includes associating the category with the query phrase.
4. The method of claim 1 wherein associating the category includes associating the category with the constituent part.
5. The method of claim 1 wherein associating the category includes associating more than one category.
6. The method of claim 1 further comprising:
receiving, based on the query phrase, a search result from the at least one identified search resource; and enabling presentation of the at least one search result to the user.
receiving, based on the query phrase, a search result from the at least one identified search resource; and enabling presentation of the at least one search result to the user.
7. The method of claim 1 further comprising:
comparing the category associated with the search query with attributes associated with the multiple search resources; and routing the query phrase to the at least one identified search resource, wherein the routing includes modifying the query phrase and routing a modified version of the query phrase to a subset of multiple search resources based on a result of the comparison.
comparing the category associated with the search query with attributes associated with the multiple search resources; and routing the query phrase to the at least one identified search resource, wherein the routing includes modifying the query phrase and routing a modified version of the query phrase to a subset of multiple search resources based on a result of the comparison.
8. The method of claim 7wherein modifying the query phrase includes at least one of adding words to the query phrase, eliminating words from the query phrase, and re-ordering words in the query phrase.
9. The method of claim 1 further coinprising:
determining an advertisement associated with at least one of the categories associated with the query phrase; and enabling presentation of the advertisement to the user.
determining an advertisement associated with at least one of the categories associated with the query phrase; and enabling presentation of the advertisement to the user.
10. The method of claim 1 further comprising training a selectional preference query classification technique, wherein the training comprises:
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent part;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and using the pattern to categorize query phrases.
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent part;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and using the pattern to categorize query phrases.
11. The method of claim 10 wherein a constituent part includes at least one of an individual word, a subportion of the training query phrase, and the entire training query phrase.
12. The method of claim 1 further comprising classifying a query phrase using at least one of a manual query classification technique and a supervised machine learning query classification technique.
13. The method of claim 12 further comprising:
comparing the results of the query classification techniques; and classifying the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
comparing the results of the query classification techniques; and classifying the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
14. The method of claim 12 further comprising:
determining a category for the query phrase using more than two query classification techniques; and classifying the query phrase using the classification arbiter and based on the classification determined by a majority of the query classification techniques.
determining a category for the query phrase using more than two query classification techniques; and classifying the query phrase using the classification arbiter and based on the classification determined by a majority of the query classification techniques.
15. The method of claim 13 wherein the classification arbiter determines the classification of the query phrase based on a confidence in the classification of the query phrase that resulted from using a query classification technique and an overall classification metric of the query classification technique.
16. The method of claim 13 further comprising:
determining a category for the query phrase using more than two query classification techniques; and classifying the query phrase using the classification arbiter and based on both the classification determined by a majority of the query classification techniques and a determination of the classification based on a confidence in the classification of the query phrase that resulted from using a query classification technique and the overall classification metric of the query classification technique.
determining a category for the query phrase using more than two query classification techniques; and classifying the query phrase using the classification arbiter and based on both the classification determined by a majority of the query classification techniques and a determination of the classification based on a confidence in the classification of the query phrase that resulted from using a query classification technique and the overall classification metric of the query classification technique.
17. The method of claim 12 wherein the manual query classification technique is used as a seed for the selectional preference and supervised machine learning query classification techniques.
18. A method, performed at least partially on a computer, for training a query classification technique, the method comprising:
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent parts;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and storing the pattern in a computer readable medium as classification information.
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent parts;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and storing the pattern in a computer readable medium as classification information.
19. The method of claim 18 wherein constituent parts includes individual words, smaller phrases within the query phrase, and the entire query phrase.
20. An apparatus for enabling satisfaction of a search responsive to a query based on classification of the query, the apparatus being configured to:
receive, from user input, a query phrase;
parse the received query phrase into constituent parts;
access, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
determine whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern, associate the category that is associated with the pattern also with the query phrase or the constituent part; and identify at least one search resource for satisfying the query phrase based on the associated category.
receive, from user input, a query phrase;
parse the received query phrase into constituent parts;
access, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
determine whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern, associate the category that is associated with the pattern also with the query phrase or the constituent part; and identify at least one search resource for satisfying the query phrase based on the associated category.
21. The apparatus of claim 20 further being configured to:
receive, based on the query phrase, a search result from the at least one identified search resource;
determine an advertisement associated with at least one of the categories associated with the query phrase; and enable presentation of the at least one search result and the advertisement to the user.
receive, based on the query phrase, a search result from the at least one identified search resource;
determine an advertisement associated with at least one of the categories associated with the query phrase; and enable presentation of the at least one search result and the advertisement to the user.
22. The apparatus of claim 20 further being configured to train a selectional preference query classification technique.
23. The apparatus of claim 20 being further configured to:
receive a training query phrase including constituent parts;
parse the training query phrase into at least one constituent part;
receive additional training query phrases having at least one constituent part in common with the training query phrase;
recognize a pattern of training query phrases having at least one common constituent part;
determine a category associated with the at least one common constituent part;
associate the pattern of training query phrases with the category associated with the at least one common constituent part; and use the pattern to categorize query phrases.
receive a training query phrase including constituent parts;
parse the training query phrase into at least one constituent part;
receive additional training query phrases having at least one constituent part in common with the training query phrase;
recognize a pattern of training query phrases having at least one common constituent part;
determine a category associated with the at least one common constituent part;
associate the pattern of training query phrases with the category associated with the at least one common constituent part; and use the pattern to categorize query phrases.
24. The apparatus of claim 20 being further configured to:
classify a query phrase using at least one of a manual query classification technique and a supervised machine learning query classification technique;
compare the results of the query classification techniques; and determine a classification for the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
classify a query phrase using at least one of a manual query classification technique and a supervised machine learning query classification technique;
compare the results of the query classification techniques; and determine a classification for the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
25. An apparatus for enabling satisfaction of a search responsive to a query based on classification of the query, the apparatus comprising:
means for receiving, from user input, a query phrase;
means for parsing the received query phrase into constituent parts;
means for accessing, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
means for determining whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
means for associating the category that is associated with the pattern also with the query phrase or the constituent part based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern; and means for identifying at least one search resource for satisfying the query phrase based on the associated category.
means for receiving, from user input, a query phrase;
means for parsing the received query phrase into constituent parts;
means for accessing, from classification information stored in a computer storage medium that includes patterns of query phrases, a pattern that is associated with at least one category;
means for determining whether a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern;
means for associating the category that is associated with the pattern also with the query phrase or the constituent part based on a determination that a constituent part parsed from the received query phrase corresponds to at least a subportion of an accessed pattern; and means for identifying at least one search resource for satisfying the query phrase based on the associated category.
26. The apparatus of claim 25 further comprising:
receiving, based on the query phrase, a search result from the at least one identified search resource;
determining an advertisement associated with at least one of the categories associated with the query phrase; and enabling presentation of the at least one search result and the advertisement to the user.
receiving, based on the query phrase, a search result from the at least one identified search resource;
determining an advertisement associated with at least one of the categories associated with the query phrase; and enabling presentation of the at least one search result and the advertisement to the user.
27. The apparatus of claim 25 further comprising training a selectional preference query classification technique, wherein the training comprises:
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent part;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and using the pattern to categorize query phrases.
receiving a training query phrase including constituent parts;
parsing the training query phrase into at least one constituent part;
receiving additional training query phrases having at least one constituent part in common with the training query phrase;
recognizing a pattern of training query phrases having at least one common constituent part;
determining a category associated with the at least one common constituent part;
associating the pattern of training query phrases with the category associated with the at least one common constituent part; and using the pattern to categorize query phrases.
28. The apparatus of claim 25 further comprising classifying a query phrase using at least one of a manual query classification technique and a supervised machine learning query classification technique.
29. The apparatus of claim 28 further comprising:
comparing the results of the query classification techniques; and determining a classification for the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
comparing the results of the query classification techniques; and determining a classification for the query phrase using a classification arbiter if the comparison indicates inconsistent results produced by the query classification techniques.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US64742405P | 2005-01-28 | 2005-01-28 | |
US60/647,424 | 2005-01-28 | ||
PCT/US2006/002817 WO2006083684A2 (en) | 2005-01-28 | 2006-01-27 | Web query classification |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2596279A1 true CA2596279A1 (en) | 2006-08-10 |
Family
ID=36777778
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002596279A Abandoned CA2596279A1 (en) | 2005-01-28 | 2006-01-27 | Web query classification |
Country Status (4)
Country | Link |
---|---|
US (3) | US7779009B2 (en) |
EP (1) | EP1854030A2 (en) |
CA (1) | CA2596279A1 (en) |
WO (1) | WO2006083684A2 (en) |
Families Citing this family (120)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1854030A2 (en) | 2005-01-28 | 2007-11-14 | Aol Llc | Web query classification |
US8615719B2 (en) | 2005-09-14 | 2013-12-24 | Jumptap, Inc. | Managing sponsored content for delivery to mobile communication facilities |
US8660891B2 (en) | 2005-11-01 | 2014-02-25 | Millennial Media | Interactive mobile advertisement banners |
US9076175B2 (en) | 2005-09-14 | 2015-07-07 | Millennial Media, Inc. | Mobile comparison shopping |
US9471925B2 (en) | 2005-09-14 | 2016-10-18 | Millennial Media Llc | Increasing mobile interactivity |
US7702318B2 (en) | 2005-09-14 | 2010-04-20 | Jumptap, Inc. | Presentation of sponsored content based on mobile transaction event |
US8156128B2 (en) | 2005-09-14 | 2012-04-10 | Jumptap, Inc. | Contextual mobile content placement on a mobile communication facility |
US20110313853A1 (en) | 2005-09-14 | 2011-12-22 | Jorey Ramer | System for targeting advertising content to a plurality of mobile communication facilities |
US10911894B2 (en) | 2005-09-14 | 2021-02-02 | Verizon Media Inc. | Use of dynamic content generation parameters based on previous performance of those parameters |
US8302030B2 (en) | 2005-09-14 | 2012-10-30 | Jumptap, Inc. | Management of multiple advertising inventories using a monetization platform |
US9058406B2 (en) | 2005-09-14 | 2015-06-16 | Millennial Media, Inc. | Management of multiple advertising inventories using a monetization platform |
US8503995B2 (en) | 2005-09-14 | 2013-08-06 | Jumptap, Inc. | Mobile dynamic advertisement creation and placement |
US7752209B2 (en) | 2005-09-14 | 2010-07-06 | Jumptap, Inc. | Presenting sponsored content on a mobile communication facility |
US8805339B2 (en) | 2005-09-14 | 2014-08-12 | Millennial Media, Inc. | Categorization of a mobile user profile based on browse and viewing behavior |
US8688671B2 (en) | 2005-09-14 | 2014-04-01 | Millennial Media | Managing sponsored content based on geographic region |
US8812526B2 (en) | 2005-09-14 | 2014-08-19 | Millennial Media, Inc. | Mobile content cross-inventory yield optimization |
US8027879B2 (en) | 2005-11-05 | 2011-09-27 | Jumptap, Inc. | Exclusivity bidding for mobile sponsored content |
US8131271B2 (en) | 2005-11-05 | 2012-03-06 | Jumptap, Inc. | Categorization of a mobile user profile based on browse behavior |
US8819659B2 (en) | 2005-09-14 | 2014-08-26 | Millennial Media, Inc. | Mobile search service instant activation |
US10038756B2 (en) | 2005-09-14 | 2018-07-31 | Millenial Media LLC | Managing sponsored content based on device characteristics |
US8290810B2 (en) | 2005-09-14 | 2012-10-16 | Jumptap, Inc. | Realtime surveying within mobile sponsored content |
US7577665B2 (en) | 2005-09-14 | 2009-08-18 | Jumptap, Inc. | User characteristic influenced search results |
US8364521B2 (en) | 2005-09-14 | 2013-01-29 | Jumptap, Inc. | Rendering targeted advertisement on mobile communication facilities |
US7860871B2 (en) | 2005-09-14 | 2010-12-28 | Jumptap, Inc. | User history influenced search results |
US10592930B2 (en) | 2005-09-14 | 2020-03-17 | Millenial Media, LLC | Syndication of a behavioral profile using a monetization platform |
US9201979B2 (en) | 2005-09-14 | 2015-12-01 | Millennial Media, Inc. | Syndication of a behavioral profile associated with an availability condition using a monetization platform |
US8103545B2 (en) | 2005-09-14 | 2012-01-24 | Jumptap, Inc. | Managing payment for sponsored content presented to mobile communication facilities |
US8229914B2 (en) | 2005-09-14 | 2012-07-24 | Jumptap, Inc. | Mobile content spidering and compatibility determination |
US7912458B2 (en) | 2005-09-14 | 2011-03-22 | Jumptap, Inc. | Interaction analysis and prioritization of mobile content |
US7769764B2 (en) | 2005-09-14 | 2010-08-03 | Jumptap, Inc. | Mobile advertisement syndication |
US7676394B2 (en) | 2005-09-14 | 2010-03-09 | Jumptap, Inc. | Dynamic bidding and expected value |
US7660581B2 (en) | 2005-09-14 | 2010-02-09 | Jumptap, Inc. | Managing sponsored content based on usage history |
US8832100B2 (en) | 2005-09-14 | 2014-09-09 | Millennial Media, Inc. | User transaction history influenced search results |
US8364540B2 (en) | 2005-09-14 | 2013-01-29 | Jumptap, Inc. | Contextual targeting of content using a monetization platform |
US8532633B2 (en) | 2005-09-14 | 2013-09-10 | Jumptap, Inc. | System for targeting advertising content to a plurality of mobile communication facilities |
US8989718B2 (en) | 2005-09-14 | 2015-03-24 | Millennial Media, Inc. | Idle screen advertising |
US8238888B2 (en) | 2006-09-13 | 2012-08-07 | Jumptap, Inc. | Methods and systems for mobile coupon placement |
US9703892B2 (en) | 2005-09-14 | 2017-07-11 | Millennial Media Llc | Predictive text completion for a mobile communication facility |
US8666376B2 (en) | 2005-09-14 | 2014-03-04 | Millennial Media | Location based mobile shopping affinity program |
US8195133B2 (en) | 2005-09-14 | 2012-06-05 | Jumptap, Inc. | Mobile dynamic advertisement creation and placement |
US8311888B2 (en) | 2005-09-14 | 2012-11-13 | Jumptap, Inc. | Revenue models associated with syndication of a behavioral profile using a monetization platform |
US8209344B2 (en) | 2005-09-14 | 2012-06-26 | Jumptap, Inc. | Embedding sponsored content in mobile applications |
US8175585B2 (en) | 2005-11-05 | 2012-05-08 | Jumptap, Inc. | System for targeting advertising content to a plurality of mobile communication facilities |
US20070174255A1 (en) * | 2005-12-22 | 2007-07-26 | Entrieva, Inc. | Analyzing content to determine context and serving relevant content based on the context |
US7904448B2 (en) * | 2006-03-29 | 2011-03-08 | Yahoo! Inc. | Incremental update of long-term and short-term user profile scores in a behavioral targeting system |
US7814109B2 (en) * | 2006-03-29 | 2010-10-12 | Yahoo! Inc. | Automatic categorization of network events |
US7809740B2 (en) * | 2006-03-29 | 2010-10-05 | Yahoo! Inc. | Model for generating user profiles in a behavioral targeting system |
US8438170B2 (en) * | 2006-03-29 | 2013-05-07 | Yahoo! Inc. | Behavioral targeting system that generates user profiles for target objectives |
US8504575B2 (en) | 2006-03-29 | 2013-08-06 | Yahoo! Inc. | Behavioral targeting system |
US20070239517A1 (en) * | 2006-03-29 | 2007-10-11 | Chung Christina Y | Generating a degree of interest in user profile scores in a behavioral targeting system |
US7483894B2 (en) * | 2006-06-07 | 2009-01-27 | Platformation Technologies, Inc | Methods and apparatus for entity search |
US8654125B2 (en) * | 2006-06-22 | 2014-02-18 | International Business Machines Corporation | System and method of chart data layout |
US8589869B2 (en) * | 2006-09-07 | 2013-11-19 | Wolfram Alpha Llc | Methods and systems for determining a formula |
US7774360B2 (en) * | 2006-09-08 | 2010-08-10 | Microsoft Corporation | Building bridges for web query classification |
US20080208975A1 (en) * | 2007-02-23 | 2008-08-28 | Olive Bentley J | Methods, systems, and computer program products for accessing a discussion forum and for associating network content for use in performing a search of a network database |
WO2008109593A2 (en) * | 2007-03-07 | 2008-09-12 | Koninklijke Philips Electronics, N.V. | Customizing diagnostic codes and descriptions for an ecg management system |
US8078604B2 (en) * | 2007-03-19 | 2011-12-13 | Microsoft Corporation | Identifying executable scenarios in response to search queries |
US7818341B2 (en) * | 2007-03-19 | 2010-10-19 | Microsoft Corporation | Using scenario-related information to customize user experiences |
US20080235170A1 (en) * | 2007-03-19 | 2008-09-25 | Microsoft Corporation | Using scenario-related metadata to direct advertising |
US7797311B2 (en) * | 2007-03-19 | 2010-09-14 | Microsoft Corporation | Organizing scenario-related information and controlling access thereto |
US8631440B2 (en) * | 2007-04-30 | 2014-01-14 | Google Inc. | Program guide user interface |
US8484192B1 (en) * | 2007-04-30 | 2013-07-09 | Google Inc. | Media search broadening |
KR100930455B1 (en) * | 2007-09-06 | 2009-12-08 | 엔에이치엔(주) | Method and system for generating search collection by query |
US9268856B2 (en) * | 2007-09-28 | 2016-02-23 | Yahoo! Inc. | System and method for inclusion of interactive elements on a search results page |
US9224149B2 (en) * | 2007-10-15 | 2015-12-29 | Google Inc. | External referencing by portable program modules |
US20100094846A1 (en) * | 2008-10-14 | 2010-04-15 | Omid Rouhani-Kalleh | Leveraging an Informational Resource for Doing Disambiguation |
US8041733B2 (en) * | 2008-10-14 | 2011-10-18 | Yahoo! Inc. | System for automatically categorizing queries |
US20100094855A1 (en) * | 2008-10-14 | 2010-04-15 | Omid Rouhani-Kalleh | System for transforming queries using object identification |
US20100094826A1 (en) * | 2008-10-14 | 2010-04-15 | Omid Rouhani-Kalleh | System for resolving entities in text into real world objects using context |
KR101045955B1 (en) * | 2008-11-14 | 2011-07-04 | 한국과학기술정보연구원 | Method for extracting semantic correlation of context, and recording device storing device and program source thereof |
US8290944B2 (en) | 2008-11-25 | 2012-10-16 | Yahoo! Inc. | Method for storing bookmarks for search results from previously submitted search queries by a user and storing links to selected documents by the user |
US9594835B2 (en) * | 2008-11-25 | 2017-03-14 | Yahoo! Inc. | Lightning search aggregate |
US8099419B2 (en) * | 2008-12-19 | 2012-01-17 | Sap Ag | Inferring rules to classify objects in a file management system |
US8108393B2 (en) * | 2009-01-09 | 2012-01-31 | Hulu Llc | Method and apparatus for searching media program databases |
US20100257171A1 (en) * | 2009-04-03 | 2010-10-07 | Yahoo! Inc. | Techniques for categorizing search queries |
US8719249B2 (en) * | 2009-05-12 | 2014-05-06 | Microsoft Corporation | Query classification |
US8788524B1 (en) | 2009-05-15 | 2014-07-22 | Wolfram Alpha Llc | Method and system for responding to queries in an imprecise syntax |
US8601015B1 (en) * | 2009-05-15 | 2013-12-03 | Wolfram Alpha Llc | Dynamic example generation for queries |
US8478779B2 (en) * | 2009-05-19 | 2013-07-02 | Microsoft Corporation | Disambiguating a search query based on a difference between composite domain-confidence factors |
US20100306214A1 (en) * | 2009-05-28 | 2010-12-02 | Microsoft Corporation | Identifying modifiers in web queries over structured data |
US8606786B2 (en) * | 2009-06-22 | 2013-12-10 | Microsoft Corporation | Determining a similarity measure between queries |
US8214363B2 (en) * | 2009-07-06 | 2012-07-03 | Abhilasha Chaudhary | Recognizing domain specific entities in search queries |
US20110125791A1 (en) * | 2009-11-25 | 2011-05-26 | Microsoft Corporation | Query classification using search result tag ratios |
US8150859B2 (en) | 2010-02-05 | 2012-04-03 | Microsoft Corporation | Semantic table of contents for search results |
US8296290B2 (en) * | 2010-02-05 | 2012-10-23 | Fti Consulting, Inc. | System and method for propagating classification decisions |
US8903794B2 (en) | 2010-02-05 | 2014-12-02 | Microsoft Corporation | Generating and presenting lateral concepts |
US8260664B2 (en) | 2010-02-05 | 2012-09-04 | Microsoft Corporation | Semantic advertising selection from lateral concepts and topics |
US20110270815A1 (en) * | 2010-04-30 | 2011-11-03 | Microsoft Corporation | Extracting structured data from web queries |
CN102236663B (en) * | 2010-04-30 | 2014-04-09 | 阿里巴巴集团控股有限公司 | Query method, query system and query device based on vertical search |
US9141702B2 (en) | 2010-06-11 | 2015-09-22 | Doat Media Ltd. | Method for dynamically displaying a personalized home screen on a device |
US9552422B2 (en) | 2010-06-11 | 2017-01-24 | Doat Media Ltd. | System and method for detecting a search intent |
US9372885B2 (en) | 2010-06-11 | 2016-06-21 | Doat Media Ltd. | System and methods thereof for dynamically updating the contents of a folder on a device |
US9529918B2 (en) | 2010-06-11 | 2016-12-27 | Doat Media Ltd. | System and methods thereof for downloading applications via a communication network |
US10713312B2 (en) | 2010-06-11 | 2020-07-14 | Doat Media Ltd. | System and method for context-launching of applications |
WO2011156605A2 (en) | 2010-06-11 | 2011-12-15 | Doat Media Ltd. | A system and methods thereof for enhancing a user's search experience |
US20120226676A1 (en) * | 2010-06-11 | 2012-09-06 | Doat Media Ltd. | System and methods thereof for adaptation of a free text query to a customized query set |
US9069443B2 (en) | 2010-06-11 | 2015-06-30 | Doat Media Ltd. | Method for dynamically displaying a personalized home screen on a user device |
US8631002B2 (en) * | 2010-12-09 | 2014-01-14 | Microsoft Corporation | Web-relevance based query classification |
US9734252B2 (en) | 2011-09-08 | 2017-08-15 | Wolfram Alpha Llc | Method and system for analyzing data using a query answering system |
CN103106214B (en) * | 2011-11-14 | 2016-02-24 | 索尼爱立信移动通讯有限公司 | A kind of candidate's phrase output intent and electronic equipment |
US9851950B2 (en) | 2011-11-15 | 2017-12-26 | Wolfram Alpha Llc | Programming in a precise syntax using natural language |
US9229974B1 (en) | 2012-06-01 | 2016-01-05 | Google Inc. | Classifying queries |
US9141665B1 (en) * | 2012-08-13 | 2015-09-22 | A9.Com, Inc. | Optimizing search system resource usage and performance using multiple query processing systems |
US9378277B1 (en) * | 2013-02-08 | 2016-06-28 | Amazon Technologies, Inc. | Search query segmentation |
US9594837B2 (en) | 2013-02-26 | 2017-03-14 | Microsoft Technology Licensing, Llc | Prediction and information retrieval for intrinsically diverse sessions |
KR20140109729A (en) | 2013-03-06 | 2014-09-16 | 한국전자통신연구원 | System for searching semantic and searching method thereof |
US8996559B2 (en) | 2013-03-17 | 2015-03-31 | Alation, Inc. | Assisted query formation, validation, and result previewing in a database having a complex schema |
US9373322B2 (en) * | 2013-04-10 | 2016-06-21 | Nuance Communications, Inc. | System and method for determining query intent |
US9864782B2 (en) * | 2013-08-28 | 2018-01-09 | AV Music Group, LLC | Systems and methods for identifying word phrases based on stress patterns |
US9411905B1 (en) * | 2013-09-26 | 2016-08-09 | Groupon, Inc. | Multi-term query subsumption for document classification |
US20150324868A1 (en) * | 2014-05-12 | 2015-11-12 | Quixey, Inc. | Query Categorizer |
US10242106B2 (en) * | 2014-12-17 | 2019-03-26 | Excalibur Ip, Llc | Enhance search assist system's freshness by extracting phrases from news articles |
US9659259B2 (en) | 2014-12-20 | 2017-05-23 | Microsoft Corporation | Latency-efficient multi-stage tagging mechanism |
US9864775B2 (en) * | 2015-03-26 | 2018-01-09 | International Business Machines Corporation | Query strength indicator |
CN106096037A (en) * | 2016-06-27 | 2016-11-09 | 北京百度网讯科技有限公司 | Search Results polymerization based on artificial intelligence, device and search engine |
US10268734B2 (en) * | 2016-09-30 | 2019-04-23 | International Business Machines Corporation | Providing search results based on natural language classification confidence information |
US11580115B2 (en) | 2017-06-29 | 2023-02-14 | Ebay Inc. | Identification of intent and non-intent query portions |
EP3798867A1 (en) * | 2019-09-26 | 2021-03-31 | Sap Se | Data querying system, data querying method, computer program product, and non-transitory storage medium |
US11709844B2 (en) | 2020-09-11 | 2023-07-25 | Volvo Car Corporation | Computerized smart inventory search methods and systems using classification and tagging |
US11914624B2 (en) * | 2020-12-10 | 2024-02-27 | Coupang Corp. | Systems and methods for managing connections in scalable clusters |
Family Cites Families (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4974191A (en) * | 1987-07-31 | 1990-11-27 | Syntellect Software Inc. | Adaptive natural language computer interface system |
JP3487644B2 (en) * | 1994-07-19 | 2004-01-19 | シャープ株式会社 | Graphical user interface creation device |
US6112201A (en) * | 1995-08-29 | 2000-08-29 | Oracle Corporation | Virtual bookshelf |
US5867799A (en) * | 1996-04-04 | 1999-02-02 | Lang; Andrew K. | Information system and method for filtering a massive flow of information entities to meet user information classification needs |
US5924105A (en) * | 1997-01-27 | 1999-07-13 | Michigan State University | Method and product for determining salient features for use in information searching |
US6505150B2 (en) * | 1997-07-02 | 2003-01-07 | Xerox Corporation | Article and method of automatically filtering information retrieval results using test genre |
US6182066B1 (en) * | 1997-11-26 | 2001-01-30 | International Business Machines Corp. | Category processing of query topics and electronic document content topics |
US6078924A (en) * | 1998-01-30 | 2000-06-20 | Aeneid Corporation | Method and apparatus for performing data collection, interpretation and analysis, in an information platform |
US6006225A (en) * | 1998-06-15 | 1999-12-21 | Amazon.Com | Refining search queries by the suggestion of correlated terms from prior searches |
US6263332B1 (en) * | 1998-08-14 | 2001-07-17 | Vignette Corporation | System and method for query processing of structured documents |
US6263362B1 (en) * | 1998-09-01 | 2001-07-17 | Bigfix, Inc. | Inspector for computed relevance messaging |
US6256664B1 (en) * | 1998-09-01 | 2001-07-03 | Bigfix, Inc. | Method and apparatus for computed relevance messaging |
US7246150B1 (en) * | 1998-09-01 | 2007-07-17 | Bigfix, Inc. | Advice provided for offering highly targeted advice without compromising individual privacy |
JP2000187435A (en) * | 1998-12-24 | 2000-07-04 | Sony Corp | Information processing device, portable apparatus, electronic pet device, recording medium with information processing procedure recorded thereon, and information processing method |
US6553347B1 (en) | 1999-01-25 | 2003-04-22 | Active Point Ltd. | Automatic virtual negotiations |
US6353823B1 (en) * | 1999-03-08 | 2002-03-05 | Intel Corporation | Method and system for using associative metadata |
US6601026B2 (en) * | 1999-09-17 | 2003-07-29 | Discern Communications, Inc. | Information retrieval by natural language querying |
US6751621B1 (en) * | 2000-01-27 | 2004-06-15 | Manning & Napier Information Services, Llc. | Construction of trainable semantic vectors and clustering, classification, and searching using trainable semantic vectors |
US6829603B1 (en) * | 2000-02-02 | 2004-12-07 | International Business Machines Corp. | System, method and program product for interactive natural dialog |
US7490091B2 (en) * | 2000-02-22 | 2009-02-10 | Harvey Lunenfeld | Metasearching a client's request for displaying at least one list comprising at least one advertisement on the client |
AU2001249123A1 (en) * | 2000-03-15 | 2001-09-24 | Hiawatha Island Software Co., Inc. | System and method for providing computer network search services |
US7213027B1 (en) * | 2000-03-21 | 2007-05-01 | Aol Llc | System and method for the transformation and canonicalization of semantically structured data |
US20010037328A1 (en) * | 2000-03-23 | 2001-11-01 | Pustejovsky James D. | Method and system for interfacing to a knowledge acquisition system |
US6523029B1 (en) * | 2000-03-24 | 2003-02-18 | Bitmobile Technologies | System and method for embedded information retrieval in a distributed free-text application environment |
US7319975B2 (en) | 2000-07-24 | 2008-01-15 | Emergency 24, Inc. | Internet-based advertising and referral system |
US6675159B1 (en) * | 2000-07-27 | 2004-01-06 | Science Applic Int Corp | Concept-based search and retrieval system |
US6633868B1 (en) * | 2000-07-28 | 2003-10-14 | Shermann Loyall Min | System and method for context-based document retrieval |
US7007008B2 (en) * | 2000-08-08 | 2006-02-28 | America Online, Inc. | Category searching |
US6766320B1 (en) * | 2000-08-24 | 2004-07-20 | Microsoft Corporation | Search engine with natural language-based robust parsing for user query and relevance feedback learning |
US20030217052A1 (en) * | 2000-08-24 | 2003-11-20 | Celebros Ltd. | Search engine method and apparatus |
US6941294B2 (en) * | 2000-08-28 | 2005-09-06 | Emotion, Inc. | Method and apparatus for digital media management, retrieval, and collaboration |
US6766316B2 (en) * | 2001-01-18 | 2004-07-20 | Science Applications International Corporation | Method and system of ranking and clustering for document indexing and retrieval |
US6778975B1 (en) * | 2001-03-05 | 2004-08-17 | Overture Services, Inc. | Search engine for selecting targeted messages |
JP2002288201A (en) * | 2001-03-23 | 2002-10-04 | Fujitsu Ltd | Question-answer processing method, question-answer processing program, recording medium for the question- answer processing program, and question-answer processor |
US7089226B1 (en) * | 2001-06-28 | 2006-08-08 | Microsoft Corporation | System, representation, and method providing multilevel information retrieval with clarification dialog |
US7526425B2 (en) * | 2001-08-14 | 2009-04-28 | Evri Inc. | Method and system for extending keyword searching to syntactically and semantically annotated data |
AU2002332971B2 (en) * | 2001-10-18 | 2008-07-03 | Yeong Kuang Oon | System and method of improved recording of medical transactions |
US7225183B2 (en) * | 2002-01-28 | 2007-05-29 | Ipxl, Inc. | Ontology-based information management system and method |
US7346606B2 (en) * | 2003-06-30 | 2008-03-18 | Google, Inc. | Rendering advertisements with documents having one or more topics using user topic interest |
US7152059B2 (en) | 2002-08-30 | 2006-12-19 | Emergency24, Inc. | System and method for predicting additional search results of a computerized database search user based on an initial search query |
US6886010B2 (en) * | 2002-09-30 | 2005-04-26 | The United States Of America As Represented By The Secretary Of The Navy | Method for data and text mining and literature-based discovery |
JP2004126840A (en) * | 2002-10-01 | 2004-04-22 | Hitachi Ltd | Document retrieval method, program, and system |
US7076497B2 (en) | 2002-10-11 | 2006-07-11 | Emergency24, Inc. | Method for providing and exchanging search terms between internet site promoters |
US7437703B2 (en) * | 2002-10-25 | 2008-10-14 | Sap Ag | Enterprise multi-agent software system with services able to call multiple engines and scheduling capability |
US20030088553A1 (en) | 2002-11-23 | 2003-05-08 | Emergency 24, Inc. | Method for providing relevant search results based on an initial online search query |
US7287025B2 (en) * | 2003-02-12 | 2007-10-23 | Microsoft Corporation | Systems and methods for query expansion |
US20040215515A1 (en) * | 2003-04-25 | 2004-10-28 | Aquantive, Inc. | Method of distributing targeted Internet advertisements based on search terms |
US7103772B2 (en) * | 2003-05-02 | 2006-09-05 | Giritech A/S | Pervasive, user-centric network security enabled by dynamic datagram switch and an on-demand authentication and encryption scheme through mobile intelligent data carriers |
US20030167212A1 (en) | 2003-05-15 | 2003-09-04 | Emergency 24, Inc. | Method and system for providing relevant advertisement internet hyperlinks |
US7613687B2 (en) * | 2003-05-30 | 2009-11-03 | Truelocal Inc. | Systems and methods for enhancing web-based searching |
US20040249808A1 (en) * | 2003-06-06 | 2004-12-09 | Microsoft Corporation | Query expansion using query logs |
US20040260677A1 (en) * | 2003-06-17 | 2004-12-23 | Radhika Malpani | Search query categorization for business listings search |
US7472118B2 (en) * | 2003-12-05 | 2008-12-30 | Microsoft Corporation | Systems and methods for improving information discovery |
US7409383B1 (en) * | 2004-03-31 | 2008-08-05 | Google Inc. | Locating meaningful stopwords or stop-phrases in keyword-based retrieval systems |
US7349901B2 (en) * | 2004-05-21 | 2008-03-25 | Microsoft Corporation | Search engine spam detection using external data |
EP1854030A2 (en) * | 2005-01-28 | 2007-11-14 | Aol Llc | Web query classification |
-
2006
- 2006-01-27 EP EP06719608A patent/EP1854030A2/en not_active Withdrawn
- 2006-01-27 US US11/340,843 patent/US7779009B2/en not_active Expired - Fee Related
- 2006-01-27 WO PCT/US2006/002817 patent/WO2006083684A2/en active Application Filing
- 2006-01-27 CA CA002596279A patent/CA2596279A1/en not_active Abandoned
-
2010
- 2010-08-02 US US12/848,318 patent/US8166036B2/en active Active
-
2012
- 2012-04-23 US US13/453,901 patent/US9424346B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
WO2006083684A3 (en) | 2010-01-28 |
US7779009B2 (en) | 2010-08-17 |
US20060190439A1 (en) | 2006-08-24 |
US20120209870A1 (en) | 2012-08-16 |
EP1854030A2 (en) | 2007-11-14 |
US9424346B2 (en) | 2016-08-23 |
US8166036B2 (en) | 2012-04-24 |
WO2006083684A2 (en) | 2006-08-10 |
US20100299290A1 (en) | 2010-11-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7779009B2 (en) | Web query classification | |
CN108268619B (en) | Content recommendation method and device | |
CA2517542C (en) | System and method for automatic generation of search results based on local intention | |
US7472113B1 (en) | Query preprocessing and pipelining | |
US8190556B2 (en) | Intellegent data search engine | |
TWI544352B (en) | System and method to facilitate matching of content to advertising information in a network | |
KR100799658B1 (en) | Host-based Intelligent Results Related to a Character Stream | |
US8572115B2 (en) | Identifying negative keywords associated with advertisements | |
EP1555625A1 (en) | Query recognizer | |
US8375048B1 (en) | Query augmentation | |
US20100257160A1 (en) | Methods & apparatus for searching with awareness of different types of information | |
US8549032B1 (en) | Determining proximity to topics of advertisements | |
US20080201219A1 (en) | Query classification and selection of associated advertising information | |
CN101957847B (en) | Searching system and implementation method thereof | |
US8244577B2 (en) | Using web-mining to enrich directory service databases and soliciting service subscriptions | |
US20080301092A1 (en) | Geocoding using information retrieval | |
NO325864B1 (en) | Procedure for calculating summary information and a search engine to support and implement the procedure | |
US8510262B2 (en) | Promoting websites based on location | |
CN101467147A (en) | Systems and methods for performing searches within vertical domains | |
US20090024623A1 (en) | System and Method to Facilitate Mapping and Storage of Data Within One or More Data Taxonomies | |
JP2008529179A (en) | Method and apparatus for accessing mobile information in natural language | |
US20100161590A1 (en) | Query processing in a dynamic cache | |
CN101379491A (en) | Method for selecting and presenting of at least one additional information | |
CN110851560B (en) | Information retrieval method, device and equipment | |
US8161065B2 (en) | Facilitating advertisement selection using advertisable units |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Dead |