Multi-feature balancing for natural language processors
US-2024419910-A1 · Dec 19, 2024 · US
US9378196B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9378196-B1 |
| Application number | US-201314065125-A |
| Country | US |
| Kind code | B1 |
| Filing date | Oct 28, 2013 |
| Priority date | Jun 27, 2013 |
| Publication date | Jun 28, 2016 |
| Grant date | Jun 28, 2016 |
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.
Methods and apparatus related to identifying a category for a task that is associated with a user and populating annotation fields related to the task based on the category of the task. The task and populated annotation fields may be provided for use by one or more application to provide a task completion step to the user. In some implementations, the category may be identified based on input from the user, documents of the user, and/or data that are associated with the user. In some implementations, a completion step for the task may be suggested to the user by an application that accesses the task and populated annotated information. In some implementations, multiple applications may suggest different completion steps to the user for the same task.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: identifying, by one or more processors, a task of a user; determining, by one or more of the processors, a category of the task; identifying, by one or more of the processors and based on the category, a plurality of annotation fields for the task; determining, by one or more of the processors, annotation field specific information related to the task, the annotation field specific information being related to one or more of the annotation fields for the task; and populating, by one or more of the processors, one or more of the annotation fields based on the annotation field specific information; determining, by one or more of the processors, a second category for the task; identifying, by one or more of the processors and based on the second category, a second plurality of annotation fields for the task, wherein at least one of the second plurality of annotation fields is unique from the plurality of annotation fields; determining, by one or more of the processors, additional annotation field specific information related to the task, the additional annotation field specific information being related to one or more of the second plurality of annotation fields for the task; and populating, by one or more of the processors, one or more of the second plurality of annotation fields based on the additional annotation field specific information. 2. The method of claim 1 , further comprising: receiving a task request, wherein the task request includes a requested category; determining the requested category is the category of the task; and providing the task and the populated annotation fields for use by one or more applications in response to the task request. 3. The method of claim 1 , wherein the category of the task is based on a category input from the user. 4. The method of claim 1 , wherein the task is identified from a document and the category of the task is determined based on a format of the document. 5. The method of claim 1 , further comprising: identifying at least one entity associated with the task; and determining at least some of the annotation field specific information related to the task based on the identified entity. 6. The method of claim 1 , wherein at least some of the annotation field specific information is based on user data associated with the user. 7. The method of claim 1 , further comprising: receiving, by a given application, the task and one or more of the populated annotation fields; determining, by the given application, a suggested completion step for the task based on the populated annotation fields; and providing, by the given application, the suggested completion step for the task to the user. 8. The method of claim 7 , wherein the suggested completion step for the task is specific to the given application. 9. The method of claim 7 , wherein the suggested completion step for the task is determined based on a subset of the populated annotation fields. 10. The method of claim 7 , wherein the step of providing the suggested completion step for the task to the user is based on user input within the given application. 11. The method of claim 7 , wherein the suggested completion step for the task is based on user movement data. 12. The method of claim 7 , further comprising: receiving, by a second given application, the task and one or more of the populated annotation fields; determining, by the second given application, a second suggested completion step for the task based on the populated annotation fields, the second suggested completion step being unique from the suggested completion step; and providing, by the second given application, the second suggested completion step for the task to the user. 13. The method of claim 1 , further comprising associating a confidence level with the category of the task, wherein the confidence level is based on the likelihood that the category of the task is correct. 14. The method of claim 1 , further comprising: determining a first confidence level for the category of the task, the first confidence level indicative of the likelihood that the category is correct for the task; and determining a second confidence level for the second category of the task, the second confidence level indicative of the likelihood that the second category is correct for the task. 15. A system, comprising: memory storing instruction; and one or more processors operable to execute the instructions stored in the memory, wherein the instructions comprise instructions to: identify a task of a user; determine a category of the task; identify, based on the category, a plurality of annotation fields for the task; determine annotation field specific information related to the task, the annotation field specific information being related to one or more of the annotation fields for the task; and populate one or more of the annotation fields based on the annotation field specific information; determine a second category for the task; identify, based on the second category, a second plurality of annotation fields for the task, wherein at least one of the second plurality of annotation fields is unique from the plurality of annotation fields; determine additional annotation field specific information related to the task, the additional annotation field specific information being related to one or more of the second plurality of annotation fields for the task; and populate one or more of the second plurality of annotation fields based on the additional annotation field specific information. 16. The system of claim 15 , wherein the instructions further include instructions to: receive a task request, wherein the task request includes a requested category; determine whether the requested category is the category of the task; and provide the task and the populated annotation fields for use by one or more applications in response to the task request. 17. The system of claim 15 , wherein at least some of the annotation field specific information is based on user data associated with the user. 18. The system of claim 15 , wherein the instructions further include instructions to: receive, by a given application, the task and one or more of the populated annotation fields; determine, by the given application, a suggested completion step for the task based on the populated annotation fields; and provide, by the given application, the suggested completion step for the task to the user. 19. The system of claim 18 , wherein the suggested completion step for the task is specific to the given application. 20. The system of claim 18 , wherein the instructions further include instructions to: receive, by a second given application, the task and one or more of the populated annotation fields; determine, by the second given application, a second suggested completion step for the task based on the populated annotation fields, the second suggested completion step being unique from the suggested completion step; and provide, by the second given application, the second suggested completion step for the task to the user. 21. The system of claim 15 , wherein the instructions further include instructions to: determine a first confidence level for the category of the task, the first confidence level indicative of the likelihood that the category is correct for the task; and determine a second confidence level for the second category of the task, the second confidence level indica
Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually · CPC title
Scheduling, planning or task assignment for a person or group · CPC title
Converting codes to words; Guess-ahead of partial word inputs · CPC title
Recognition of textual entities · CPC title
Form filling; Merging · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.