Avoiding supporting evidence processing when evidence scoring does not affect final ranking of a candidate answer
US-2016180249-A1 · Jun 23, 2016 · US
US10353976B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10353976-B2 |
| Application number | US-201514874982-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 5, 2015 |
| Priority date | Oct 5, 2015 |
| Publication date | Jul 16, 2019 |
| Grant date | Jul 16, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method includes receiving a search query containing one or more query terms from a remote device and identifying an entity in the search query. The entity is a known entity name of a known entity type. The method also includes determining a set of alternate search queries based on the identified entity. The alternate search queries are configured to identify states of software applications that correspond to entities that are substitutes for the identified entity. The method also includes identifying a consideration set of application state records stored in an application state data store based on the alternate set of search queries. Each application state record defines a state of a respective software application that is at least relevant to one or more of the alternate search queries. The method also includes generating search results based on the consideration set and transmitting the search results to the remote device.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by at least one processor, a search query containing at least one query term from a remote device; identifying, by the at least one processor, an entity in the search query, the entity being a known entity name of a known entity type; generating, by the at least one processor, a set of alternate search queries based on the entity, the alternate search queries being configured to identify states of applications that correspond to entities that are substitutes for the entity; identifying, by the at least one processor, a consideration set of application state records stored in an application state data store based on the set of alternate search queries, each application state record defining a state of a respective application that is at least relevant to at least one of the alternate search queries; generating, by the at least one processor, search results based on the consideration set; and transmitting, by the at least one processor, the search results to the remote device, wherein the set of alternate search queries is generated by: obtaining, by the at least one processor, a first set of documents by crawling at least one application, separating, by the at least one processor, the first set of documents into first and second subsets, the first subset containing documents relating to the entity or related entities and the second subset containing documents not related to the entity or the related entities, extracting, by the at least one processor, at least one feature that differentiates the documents in the first subset and the documents in the second subset, and generating, by the at least one processor, the set of alternate search queries based on the at least one extracted feature. 2. The method of claim 1 , wherein generating the set of alternate search queries includes: querying a query lookup table with an entity ID of the entity or a combination of an entity name of the entity and an entity type indicating a classification of the identified entity; and receiving the set of alternate search queries from the query lookup table. 3. The method of claim 2 , wherein generating the set of alternate search queries further includes: determining one or more query constraints based on the entity type and one or more context parameters received with the search query; and adding the constraints to each of the set of alternate search queries. 4. The method of claim 1 , wherein at least a subset of the set of alternate search queries are application-specific search queries, and wherein an application-specific search query is constrained to application state records corresponding to a single application. 5. The method of claim 1 further comprising: determining, by the at least one processor, a constraint rule from a plurality of constraint rules based on an entity type of the identified entity; determining, by the at least one processor, a location constraint for the search query based on the constraint rule and a location of a user device that transmitted the search query; and generating, by the at least one processor, a constrained search query based on the location constraint and the search query, wherein the consideration set if further identified based on the constrained search query. 6. The method of claim 5 , wherein identifying the consideration set includes: querying a search index based on the constrained search query, the search index identifying zero or more application state records that are relevant to the constrained search query; determining whether a number of application state records identified by the search index exceeds a threshold; and when the number of application state records does not exceed the threshold, querying the search index based on the set of alternate search queries. 7. The method of claim 1 , wherein the set of alternate search queries is learned off line and is stored in relation to an entity identifier of the entity in an alternate query data store. 8. The method of claim 1 , wherein the set of alternate search queries is generated by: obtaining a second set of documents, by the at least one processor, by crawling a content rich application; clustering, by the at least one processor, the second set of documents into a plurality of groups based on features defined in the documents; identifying, by the at least one processor, a group of documents from the plurality of groups that contains a document corresponding to the entity; identifying, by the at least one processor, other entities referenced by other documents in the group of documents to obtain the related entities; obtaining the first set of documents, by the at least one processor, by crawling at least one other application; separating, by the at least one processor, the first set of documents into the first and second subsets; extracting, by the at least one processor, the at least one feature that differentiates the documents in the first subset and the documents in the second subset; and generating, by the at least one processor, the set of alternate search queries based on the at least one extracted feature. 9. The method of claim 1 wherein the remote device is a user device on which the search query was provided. 10. A search system comprising: a network interface; at least one storage device, the at least one storage device storing: an application state data store that stores a plurality of application state records, each application state record defining a state of a respective application; and an alternate query data store that stores a query lookup table, the query lookup table respectively relating entities to a corresponding set of alternate search queries, each set of alternate search queries corresponding to a respective entity and being configured to identify states of applications that correspond to entities that are substitutes for the corresponding entity; and at least one processor that executes computer-readable instructions, the computer-readable instructions causing the at least one processor to: receive a search query containing at least one query term from a remote device via the network interface; identify an entity in the search query, the entity being a known entity name of a known entity type; generate a set of alternate search queries based on the entity; identify a consideration set of application state records based on the set of alternate search queries; generate search results based on the consideration set; and transmit the search results to the remote device, wherein the set of alternate search queries is generated by: obtaining a first set of documents by crawling at least one application, separating the first set of documents into first and second subsets, the first subset containing documents relating to the entity or related entities and the second subset containing documents not related to the entity or the related entities, extracting at least one feature that differentiate the documents in the first subset and the documents in the second subset, and generating the set of alternate search queries based on the at least one extracted feature. 11. The search system of claim 10 , wherein generating the set of alternate search queries includes: querying the query lookup table with an entity ID of the entity or a combination of an entity name of the entity and an entity type indicating a classification of the identified entity; and receiving the set of alternate search queries from the query lookup table. 12. The search system of claim 11 , wherein generating the set of alternate search queries further includes: determin
Iterative querying; Query formulation based on the results of a preceding query · CPC title
Spatial or temporal dependent retrieval, e.g. spatiotemporal queries · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.