US20120117077A1 - Annotation Framework - Google Patents
Annotation Framework Download PDFInfo
- Publication number
- US20120117077A1 US20120117077A1 US13/292,030 US201113292030A US2012117077A1 US 20120117077 A1 US20120117077 A1 US 20120117077A1 US 201113292030 A US201113292030 A US 201113292030A US 2012117077 A1 US2012117077 A1 US 2012117077A1
- Authority
- US
- United States
- Prior art keywords
- fact
- facts
- value
- repository
- annotation
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/169—Annotation, e.g. comment data or footnotes
-
- 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
Definitions
- This invention pertains in general to searching collections of data and, in particular, to ways of adding detecting information in such collections of data.
- the World Wide Web and other information storage and retrieval systems contain a great deal of information. People have devised many ways of organizing and viewing this information.
- the described embodiments of the present invention provide a methodology and system for storing annotations of facts stored in a repository in association with objects.
- the fact repository includes a large collection of facts, each of which is associated with an object, such as a person, place, book, movie, country, or any other entity of interest.
- Each fact comprises an attribute, which is descriptive of the type of fact (e.g., “name,” or “population”) and a value for that attribute (e.g., “George Washington”, or “1,397,264,580”).
- a value can also contain any amount of text—from a single term or phrase to many paragraphs or pages—such as appropriate to describe the attribute.
- Each object will have a name fact that is the name of the object.
- the value can include one or more phrases that are themselves the names of other facts.
- annotations are stored corresponding to some of the facts in the repository.
- Some annotations for example, represent number values in the facts, while other annotation values represent dates, geographic locations, ISBN values, names, units, and so on.
- Annotations are passed to requesting objects in response to queries and are used to determine search results Annotations are also used to decide whether facts match and whether facts contain reasonable values.
- FIG. 1 shows a system architecture, in accordance with an embodiment of the invention.
- FIGS. 2( a )- 2 ( d ) are block diagrams illustrating a data structure for facts within a repository of FIG. 1 in accordance with preferred embodiments of the invention.
- FIG. 2( e ) is a block diagram illustrating an alternate data structure for facts and objects in accordance with preferred embodiments of the invention.
- FIG. 2( f ) shows a plurality of annotations associated with facts in a repository.
- FIG. 2( g ) shows an example of two facts and an associated annotation of one of the facts.
- FIGS. 3( a )- 3 ( c ) are flow charts showing methods of creating and using annotations.
- FIG. 4 is a block diagram showing annotation creation.
- FIG. 5 is a flow chart showing annotation creation.
- FIG. 6 shows an example of an XML feed sent in response to a request from on object requester and including annotations.
- FIG. 1 shows a system architecture 100 adapted to support one embodiment of the invention.
- FIG. 1 shows components used to add facts into, and retrieve facts from a repository 115 .
- the system architecture 100 includes a network 104 , through which any number of document hosts 102 communicate with a data processing system 106 , along with any number of object requesters 152 , 154 .
- Document hosts 102 store documents and provide access to documents.
- a document is comprised of any machine-readable data including any combination of text, graphics, multimedia content, etc.
- a document may be encoded in a markup language, such as Hypertext Markup Language (HTML), i.e., a web page, in an interpreted language (e.g., JavaScript) or in any other computer readable or executable format.
- HTML Hypertext Markup Language
- a document can include one or more hyperlinks to other documents.
- a typical document will include one or more facts within its content.
- a document stored in a document host 102 may be located and/or identified by a Uniform Resource Locator (URL), or Web address, or any other appropriate form of identification and/or location.
- URL Uniform Resource Locator
- a document host 102 is implemented by a computer system, and typically includes a server adapted to communicate over the network 104 via networking protocols (e.g., TCP/IP), as well as application and presentation protocols (e.g., HTTP, HTML, SOAP, D-HTML, Java).
- networking protocols e.g., TCP/IP
- application and presentation protocols e.g., HTTP, HTML, SOAP, D-HTML, Java.
- the documents stored by a host 102 are typically held in a file directory, a database, or other data repository.
- a host 102 can be implemented in any computing device (e.g., from a PDA or personal computer, a workstation, mini-computer, or mainframe, to a cluster or grid of computers), as well as in any processor architecture or operating system.
- FIG. 1 shows components used to manage facts in a fact repository 115 .
- Data processing system 106 includes one or more importers 108 , one or more janitors 110 , a build engine 112 , a service engine 114 , and a fact repository 115 (also called simply a “repository”).
- Importers 108 operate to process documents received from the document hosts, read the data content of documents, and extract facts (as operationally and programmatically defined within the data processing system 106 ) from such documents.
- the importers 108 also determine the subject or subjects with which the facts are associated, and extract such facts into individual items of data, for storage in the fact repository 115 .
- there are different types of importers 108 for different types of documents for example, dependent on the format or document type.
- Janitors 110 operate to process facts extracted by importer 108 .
- This processing can include but is not limited to, data cleansing, object merging, and fact induction.
- Other types of janitors 110 may be implemented, depending on the types of data management functions desired, such as translation, compression, spelling or grammar correction, and the like.
- Various janitors 110 act on facts to normalize attribute names, and values and delete duplicate and near-duplicate facts so an object does not have redundant information. For example, we might find on one page that Britney Spears's birthday is “12/2/1981” while on another page that her date of birth is “Dec. 2, 1981.” Birthday and Date of Birth might both be rewritten as Birthdate by one janitor and then another janitor might notice that 12/2/1981 and Dec. 2, 1981 are different forms of the same date. It would choose the preferred form, remove the other fact and combine the source lists for the two facts. As a result when you look at the source pages for this fact, on some you'll find an exact match of the fact and on others text that is considered to be synonymous with the fact.
- Build engine 112 builds and manages the repository 115 .
- Service engine 114 is an interface for querying the repository 115 .
- Service engine 114 's main function is to process queries, score matching objects, and return them to the caller but it is also used by janitor 110 .
- Repository 115 stores factual information extracted from a plurality of documents that are located on document hosts 102 .
- a document from which a particular fact may be extracted is a source document (or “source”) of that particular fact.
- source a source of a fact includes that fact (or a synonymous fact) within its contents.
- Repository 115 contains one or more facts.
- each fact is associated with exactly one object.
- One implementation for this association includes in each fact an object ID that uniquely identifies the object of the association.
- any number of facts may be associated with an individual object, by including the object ID for that object in the facts.
- objects themselves are not physically stored in the repository 115 , but rather are defined by the set or group of facts with the same associated object ID, as described below. Further details about facts in repository 115 are described below, in relation to FIGS. 2( a )- 2 ( d ).
- the components of the data processing system 106 will be distributed over multiple computers, communicating over a network.
- repository 115 may be deployed over multiple servers.
- the janitors 110 may be located on any number of different computers. For convenience of explanation, however, the components of the data processing system 106 are discussed as though they were implemented on a single computer.
- document hosts 102 are located on data processing system 106 instead of being coupled to data processing system 106 by a network.
- importer 108 may import facts from a database that is a part of or associated with data processing system 106 .
- FIG. 1 also includes components to access repository 115 on behalf of one or more object requesters 152 , 154 .
- Object requesters are entities that request objects from repository 115 .
- Object requesters 152 , 154 may be understood as clients of the system 106 , and can be implemented in any computer device or architecture.
- a first object requester 152 is located remotely from system 106
- a second object requester 154 is located in data processing system 106 .
- the blog may include a reference to an object whose facts are in repository 115 .
- An object requester 152 such as a browser displaying the blog will access data processing system 106 so that the information of the facts associated with the object can be displayed as part of the blog web page.
- janitor 110 or other entity considered to be part of data processing system 106 can function as object requester 154 , requesting the facts of objects from repository 115 .
- FIG. 1 shows that data processing system 106 includes a memory 107 and one or more processors 116 .
- Memory 107 includes importers 108 , janitors 110 , build engine 112 , service engine 114 , and requester 154 , each of which are preferably implemented as instructions stored in memory 107 and executable by processor 116 .
- Memory 107 also includes repository 115 .
- Repository 115 can be stored in a memory of one or more computer systems or in a type of memory such as a disk.
- FIG. 1 also includes a computer readable medium 118 containing, for example, at least one of importers 108 , janitors 110 , build engine 112 , service engine 114 , requester 154 , and at least some portions of repository 115 .
- FIG. 1 also includes a computer readable medium 118 containing, for example, at least one of importers 108 , janitors 110 , build engine 112 , service engine 114 , requester 154 ,
- data processing system 106 also includes one or more input/output devices 120 that allow data to be input and output to and from data processing system 106 .
- data processing system 106 preferably also includes standard software components such as operating systems and the like and further preferably includes standard hardware components not shown in the figure for clarity of example.
- FIG. 2( a ) shows an example format of a data structure for facts within repository 115 , according to some embodiments of the invention.
- the repository 115 includes facts 204 .
- Each fact 204 includes a unique identifier for that fact, such as a fact ID 210 .
- Each fact 204 includes at least an attribute 212 and a value 214 .
- a fact associated with an object representing George Washington may include an attribute of “date of birth” and a value of “Feb. 22, 1732.”
- all facts are stored as alphanumeric characters since they are extracted from web pages.
- facts also can store binary data values.
- Other embodiments, however, may store fact values as mixed types, or in encoded formats.
- each fact is associated with an object ID 209 that identifies the object that the fact describes.
- object ID 209 identifies the object that the fact describes.
- objects are not stored as separate data entities in memory.
- the facts associated with an object contain the same object ID, but no physical object exists.
- objects are stored as data entities in memory, and include references (for example, pointers or IDs) to the facts associated with the object.
- the logical data structure of a fact can take various forms; in general, a fact is represented by a tuple that includes a fact ID, an attribute, a value, and an object ID.
- the storage implementation of a fact can be in any underlying physical data structure.
- FIG. 2( b ) shows an example of facts having respective fact IDs of 10 , 20 , and 30 in repository 115 .
- Facts 10 and 20 are associated with an object identified by object ID “ 1 .”
- Fact 10 has an attribute of “Name” and a value of “China.”
- Fact 20 has an attribute of “Category” and a value of “Country.”
- the object identified by object ID “ 1 ” has a name fact 205 with a value of “China” and a category fact 206 with a value of “Country.”
- Fact 30 208 has an attribute of “Property” and a value of “Bill Clinton was the 42nd President of the United States from 1993 to 2001.”
- the object identified by object ID “ 2 ” has a property fact with a fact ID of 30 and a value of “Bill Clinton was the 42nd President of the United States from 1993 to 2001.”
- each fact has one attribute and one value.
- the number of facts associated with an object is not limited; thus while only two facts are shown for the “China” object, in practice there may be dozens, even hundreds of facts associated with a given object.
- the value fields of a fact need not be limited in size or content. For example, a fact about the economy of “China” with an attribute of “Economy” would have a value including several paragraphs of text, numbers, perhaps even tables of figures. This content can be formatted, for example, in a markup language. For example, a fact having an attribute “original html” might have a value of the original html text taken from the source web page.
- FIG. 2( b ) shows the explicit coding of object ID, fact ID, attribute, and value
- content of the fact can be implicitly coded as well (e.g., the first field being the object ID, the second field being the fact ID, the third field being the attribute, and the fourth field being the value).
- Other fields include but are not limited to: the language used to state the fact (English, etc.), how important the fact is, the source of the fact, a confidence value for the fact, and so on.
- FIG. 2( c ) shows an example object reference table 210 that is used in some embodiments. Not all embodiments include an object reference table.
- the object reference table 210 functions to efficiently maintain the associations between object IDs and fact IDs. In the absence of an object reference table 210 , it is also possible to find all facts for a given object ID by querying the repository to find all facts with a particular object ID. While FIGS. 2( b ) and 2 ( c ) illustrate the object reference table 210 with explicit coding of object and fact IDs, the table also may contain just the ID values themselves in column or pair-wise arrangements.
- FIG. 2( d ) shows an example of a data structure for facts within repository 115 , according to some embodiments of the invention showing an extended format of facts.
- the fields include an object reference link 216 to another object.
- the object reference link 216 can be an object ID of another object in the repository 115 , or a reference to the location (e.g., table row) for the object in the object reference table 210 .
- the object reference link 216 allows facts to have as values other objects. For example, for an object “United States,” there may be a fact with the attribute of “president” and the value of “George W. Bush,” with “George W. Bush” being an object having its own facts in repository 115 .
- the value field 214 stores the name of the linked object and the link 216 stores the object identifier of the linked object.
- this “president” fact would include the value 214 of “George W. Bush”, and object reference link 216 that contains the object ID for the for “George W. Bush” object.
- facts 204 do not include a link field 216 because the value 214 of a fact 204 may store a link to another object.
- Each fact 204 also may include one or more metrics 218 .
- a metric provides an indication of the some quality of the fact.
- the metrics include a confidence level and an importance level.
- the confidence level indicates the likelihood that the fact is correct.
- the importance level indicates the relevance of the fact to the object, compared to other facts for the same object.
- the importance level may optionally be viewed as a measure of how vital a fact is to an understanding of the entity or concept represented by the object.
- Each fact 204 includes a list of one or more sources 220 that include the fact and from which the fact was extracted.
- Each source may be identified by a Uniform Resource Locator (URL), or Web address, or any other appropriate form of identification and/or location, such as a unique document identifier.
- URL Uniform Resource Locator
- the facts illustrated in FIG. 2( d ) include an agent field 222 that identifies the importer 108 that extracted the fact.
- the importer 108 may be a specialized importer that extracts facts from a specific source (e.g., the pages of a particular web site, or family of web sites) or type of source (e.g., web pages that present factual information in tabular form), or an importer 108 that extracts facts from free text in documents throughout the Web, and so forth.
- a name fact 207 is a fact that conveys a name for the entity or concept represented by the object ID.
- a name fact 207 includes an attribute 224 of “name” and a value, which is the name of the object. For example, for an object representing the country Spain, a name fact would have the value “Spain.”
- a name fact 207 being a special instance of a general fact 204 , includes the same fields as any other fact 204 ; it has an attribute, a value, a fact ID, metrics, sources, etc.
- the attribute 224 of a name fact 207 indicates that the fact is a name fact, and the value is the actual name.
- the name may be a string of characters.
- An object ID may have one or more associated name facts, as many entities or concepts can have more than one name. For example, an object ID representing Spain may have associated name facts conveying the country's common name “Spain” and the official name “Kingdom of Spain.” As another example, an object ID representing the U.S. Patent and Trademark Office may have associated name facts conveying the agency's acronyms “PTO” and “USPTO” as well as the official name “United States Patent and Trademark Office.” If an object does have more than one associated name fact, one of the name facts may be designated as a primary name and other name facts may be designated as secondary names, either implicitly or explicitly.
- a property fact 208 is a fact that conveys a statement about the entity or concept represented by the object ID.
- Property facts are generally used for summary information about an object.
- a property fact 208 being a special instance of a general fact 204 , also includes the same parameters (such as attribute, value, fact ID, etc.) as other facts 204 .
- the attribute field 226 of a property fact 208 indicates that the fact is a property fact (e.g., attribute is “property”) and the value is a string of text that conveys the statement of interest.
- the value of a property fact may be the text string “Bill Clinton was the 42nd President of the United States from 1993 to 2001.”
- Some object IDs may have one or more associated property facts while other objects may have no associated property facts.
- the data structure of the repository 115 may take on other forms. Other fields may be included in facts and some of the fields described above may be omitted.
- each object ID may have additional special facts aside from name facts and property facts, such as facts conveying a type or category (for example, person, place, movie, actor, organization, etc.) for categorizing the entity or concept represented by the object ID.
- an object's name(s) and/or properties may be represented by special records that have a different format than the general facts records 204 .
- null object As described previously, a collection of facts is associated with an object ID of an object.
- An object may become a null or empty object when facts are disassociated from the object.
- a null object can arise in a number of different ways.
- One type of null object is an object that has had all of its facts (including name facts) removed, leaving no facts associated with its object ID.
- Another type of null object is an object that has all of its associated facts other than name facts removed, leaving only its name fact(s).
- the object may be a null object only if all of its associated name facts are removed.
- a null object represents an entity or concept for which the data processing system 106 has no factual information and, as far as the data processing system 106 is concerned, does not exist.
- facts of a null object may be left in the repository 115 , but have their object ID values cleared (or have their importance to a negative value). However, the facts of the null object are treated as if they were removed from the repository 115 . In some other embodiments, facts of null objects are physically removed from repository 115 .
- FIG. 2( e ) is a block diagram illustrating an alternate data structure 290 for facts and objects in accordance with preferred embodiments of the invention.
- an object 290 contains an object ID 292 and references or points to facts 294 .
- Each fact includes a fact ID 295 , an attribute 297 , and a value 299 .
- an object 290 actually exists in memory 107 .
- the content of the facts in the repository 115 is also indexed in index 127 .
- the index 127 maintains a term index, which maps terms to ⁇ object, fact, field, token ⁇ tuples, where “field” is, e.g., attribute or value.
- the service engine 114 is adapted to receive keyword queries from clients such as object requestors, and communicates with the index 127 to retrieve the facts that are relevant to user's search query. For a generic query containing one or more terms, the service engine 114 assumes the scope is at the object level. Thus, any object with one or more of the query terms somewhere (not necessarily on the same fact) will match the query for purposes of being ranked in the search results.
- the ranking (score) of an object is a linear combination of relevance scores for each of the facts.
- the relevance score for each fact is based on whether the fact includes one or more query terms (a hit) in, for example, one of the attribute, value, or source portion of the fact.
- Each hit is scored based on the frequency of the term that is hit, with more common terms getting lower scores, and rarer terms getting higher scores (e.g., using a TF-IDF based term weighting model).
- the fact score is then adjusted based on additional factors.
- each fact's score is also adjusted by its associated confidence measure and by its importance measure. Since each fact is independently scored, the facts most relevant and important to any individual query can be determined, and selected. In one embodiment, a selected number (e.g., 5) of the top scoring facts is selected for display in response to a query.
- facts can have associated “annotations.” Annotations are subsets of snippets of the fact's value that are used to provide additional information about facts. Often, an annotation has a high confidence level, especially if it has been entered by a human being or somehow otherwise corroborated. For example, the string “New York, N.Y.” can be used to generate a map plot, but an annotation can associate a latitude and longitude with that string and the latitude/longitude can be plotted on a map. As another example, the Britney Spears object has a large number of facts relating to Britney Spears. Annotations exist for such facts as her birthday, wedding anniversary, and birthplace. It is possible to compare annotations of various facts to determine whether a fact has reasonable values. Certain types of information such as numbers, dates, and locations are good candidates for becoming annotations, as discussed in detail below.
- FIG. 2( f ) shows a format of a plurality of annotations associated with facts in repository 115 in an embodiment of the invention.
- the Figure shows three types of annotations (although there can be other types of annotations): Number annotations 296 , date annotations 297 , and GeoPoint (GeoPt) annotations 298 .
- Each annotation has at least a fact ID, a beginning index in the value of the fact with the fact ID, and a length within the value of the fact value.
- the fact ID identifies which fact the annotation is associated with.
- the beginning index is an index into the fact's value where the annotation value begins.
- the length is a length of the annotation value within the fact's value.
- FIG. 2( g ) shows an example of two facts and an associated annotation of one of the facts.
- a fact 10 has a value of “Britney Spears was born Dec. 2, 1981”
- a date annotation associated with that fact might have the fact ID 282 of fact 10 , an index of 284 (because the date starts on character 25, indexed from 1), and a length 286 of 16 (because the date is 16 characters long). (Other embodiments index from 0.)
- each type of fact is stored together (i.e., all the number facts together, etc).
- annotation types are not necessarily stored together.
- all fact values including numeric values dates, latitude and longitude are stored in repository 115 as characters.
- Some embodiments also store a copy of the annotation value (for example “Dec. 2, 1981”) with the annotation.
- Other embodiments store a pointer or reference into the appropriate fact to retrieve the annotation value.
- Other embodiments store the annotations as part of the facts instead of separately.
- index annotations in index 127 causing them to be searchable.
- annotations can be used when “vetting” facts stored in repository 115 . Such an operation might be performed by janitor 110 or by any appropriate entity. For a fact received for review in step 322 , janitor 110 determines 324 whether the fact is duplicated by other facts in the repository. For example, two facts may contain the same information in different formats. For example, a plurality of facts might have annotations that indicate or suggest that string values of “10 million”, “10,000,000”, and “10000000.000” all represent the same value. As another example, a first fact may contain a distance value in metric format, while a second fact might contain the same distance in Imperial format. In some embodiments, comparison of annotations alone is sufficient to determine duplicates. In other embodiments, comparison of annotations is an initial step and janitors 110 can go on to make more accurate comparisons using the candidates identified by annotations. Thus, annotations can also be used as an initial screening device to find duplicate facts.
- janitor 110 can also use annotations to determine 326 whether the fact has a reasonable value. For example, if there exists an annotation for Britney Spears's birthplace stating that it is “Louisiana”, then janitor 110 may use that information to vet the large numbers of facts associated with the Britney Spears object.
- the Britney Spears's birthplace annotation may have been automatically generated or it may have been hand-entered and vetted by a human being (the latter presumably being more trustworthy).
- the service engine can use annotations to determine which facts to send in response to a query. Facts having values in accordance with corresponding annotation values are given preference.
- FIGS. 3( b ) and 3 ( c ) are flow charts showing additional methods of using annotations.
- FIG. 3( b ) shows an method where a query is received 352 (for example by object service 114 ). The object service determines 354 a plurality of facts that match the query. Then the object service determines 356 one or more facts that correspond to the determined facts and returns 358 the facts and the annotations. Thus, if the query is “Britney Spears” object service 114 would determine that the facts of FIG. 2( g ) match and would also determine that the annotation of FIG. 2( g ) matches since it corresponds to facts that match the query. In this method, annotations are returned in addition to facts because they provide a fast way to locate pertinent data in the facts without a real-time search of the fact values.
- FIG. 3( c ) is a flow chart showing use of annotations to help select facts.
- a query is received 362 (for example by object service 114 ).
- the object service determines 366 a plurality of annotations that are relevant to the query. Relevance of annotations can be determined, for example, by accessing the index 127 if annotations are indexed, by accessing a separate annotation index (not shown) if annotations are separately indexed, by searching the values of the annotations, or by any other appropriate method. Then the object service determines 366 one or more facts that correspond to the determined annotations and returns 368 the facts. In some embodiments, the annotations are also returned.
- the query is “Britney Spears's birthday” object service 114 would determine that the annotation of FIG. 2( g ) matches and would also determine that fact 10 is associated with that annotation. Some embodiments would return only fact 10 . Other embodiments would return fact 10 and other facts of the “Britney Spears” object that is associated with fact 10 . Some embodiments may also return the annotation itself. In this method, annotations are used because they provide a fast way to locate pertinent data in the facts without a real-time search through the fact values.
- Annotations can also be used by service engine 114 to identify erroneous facts that do not match annotation values.
- FIG. 4 is a block diagram showing one method of annotation creation.
- FIG. 5 is a flow chart showing annotation creation.
- a recognizer 402 is preferably implemented as a software program or hardware device. It examines 504 facts in repository 115 to extract annotation values. Recognizers may recognize, for example, dates, numbers, locations (which are used to create GeoPt annotations), distances, directions, ISBN numbers, names of persons, measurements, height, weight, mass, volume, and so on. As another example, measurements can be annotated to include units such as “10 meters”, “100 degrees Fahrenheit, and so on. Extracted annotations are encoded in one or more appropriately sized annotation blocks 506 as shown in FIG. 2( f ) with a fact ID, index, and length. In some embodiments, the annotation blocks are compacted 508 before being stored 510 in repository 115 or other appropriate storage. In other embodiments, annotations are added by human beings. In other embodiments, some annotations are added by human beings and some are automatically generated. In some embodiments, annotations added by human beings are given a higher confidence value than annotations that are automatically created.
- annotations can be returned in response to a query.
- This query can be, for example, a browser-based query, in which case, the annotations are returned with the query results.
- the annotations can be mixed in with the query results or can be displayed separately. For example, annotations can be displayed separately at the top of a results web page.
- Queries can also take the form of requests for XML feeds or other formats of data feeds.
- an entry corresponds to an object and each atom corresponds to a fact in the object.
- An object can have more than one associated fact.
- This example uses the Atom format, although any appropriate feed format can be used.
- each object has an associated object ID 601 (in this example “1a27a12f0de4b506a93022496b370c40”).
- the feed includes a plurality of facts 602 , 604 , 606 .
- Fact 602 shows an example of a fact having an attribute and an attribute value, along with a link representing a source of the fact.
- Fact 602 has a fact with a value containing the string “China”.
- Facts 604 and 606 do not contain the query string “China,” but are returned because they are facts associated with the same object as fact 602 .
- Some embodiments return partial facts as well as or in addition to complete facts. For example, a query for the date of birth attribute for object number 2038472038 might just return “Jun. 17, 1974” and no other facts for that object.
- Fact 604 also includes an attribute and a value, and further includes an annotation.
- an annotation is associated with a fact in repository 115 .
- the feed for fact 604 has an attribute and a value:
- the feed for fact 604 also has a source link:
- the feed for fact 604 also has two associated annotations:
- each annotation has a beginning index, a length, and a value.
- One of the annotations is a number annotation with a value of “1306313812”.
- the other annotation is a date annotation with a value of “July 2005”.
- a date annotation has separate fields for month, day, and year.
- a geopoint annotation represents a latitude and longitude associated with a fact. Geopoint annotations are noteworthy at least because they contain a two-part value (latitude and longitude). Other types of annotations can have two-or-more-part values as well. Note that in this example, the latitude and longitude values themselves do not appear in the fact. Instead, the value “Washington, District of Columbia, 20008” appears. At some point, an annotation was created for the latitude and longitude of Washington, D.C. and stored in association with that fact (and most likely with all other facts containing a mention of “Washington, D.C.”).
- annotations can be used in the present invention, including but not limited to: name annotations, isbn annotations, units (to indicate a unit for numerical values).
- the feed received by an object requester can be used in a number of ways, including but not limited to display and calculation.
- Some embodiments also support an “alt” parameter, which allows the user to specify the format of the results. It has three possible values: “atom” (the default), “rss”, “osrss”.
- Certain aspects of the present invention include process steps and instructions described herein in the form of an algorithm. It should be noted that the process steps and instructions of the present invention could be embodied in software, firmware or hardware, and when embodied in software, could be downloaded to reside on and be operated from different platforms used by real time network operating systems.
- the present invention also relates to an apparatus for performing the operations herein.
- This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored on a computer readable medium that can be accessed by the computer.
- a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
- the computers referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.
- the present invention is well suited to a wide variety of computer network systems over numerous topologies.
- the configuration and management of large networks comprise storage devices and computers that are communicatively coupled to dissimilar computers and storage devices over a network, such as the Internet.
Abstract
A fact repository contains facts having attributes and values and further having associated annotations, which are used, among other things, to vet facts in the repository and which can be returned in response to a query.
Description
- This application is a divisional application of U.S. patent application Ser. No. 11/356,728, filed Feb. 17, 2006, entitled “Annotation Framework”, which is incorporated by reference herein in its entirety.
- This application is related to the following U.S. Applications, all of which are incorporated by reference herein in their entirety:
-
- U.S. application Ser. No. 11/357,748, entitled “Support for Object Search”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/342,290, entitled “Data Object Visualization”, filed on Jan. 27, 2006;
- U.S. application Ser. No. 11/342,293, entitled “Data Object Visualization Using Maps”, filed on Jan. 27, 2006;
- U.S. application Ser. No. 11/356,679, entitled “Query Language”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/356,837, entitled “Automatic Object Reference Identification and Linking in a Browseable Fact Repository”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/356,851, entitled “Browseable Fact Repository”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/356,842, entitled “ID Persistence Through Normalization”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/341,069, entitled “Object Categorization for Information Extraction”, filed on Jan. 27, 2006;
- U.S. application Ser. No. 11/356,838, entitled “Modular Architecture for Entity Normalization”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/356,765, entitled “Attribute Entropy as a Signal in Object Normalization”, filed Feb. 17, 2006;
- U.S. application Ser. No. 11/341,907, entitled “Designating Data Objects for Analysis”, filed on Jan. 27, 2006; and
- U.S. application Ser. No. 11/342,277, entitled “Data Object Visualization Using Graphs”, filed on Jan. 27, 2006.
- 1. Field of the Invention
- This invention pertains in general to searching collections of data and, in particular, to ways of adding detecting information in such collections of data.
- 2. Description of the Related Art
- The World Wide Web and other information storage and retrieval systems contain a great deal of information. People have devised many ways of organizing and viewing this information.
- As the retrieval and storage of information on the Internet continues to evolve, information is being stored in many different formats besides web pages. Moreover, in a very large repository of data, it becomes difficult to search the data in real-time. What is needed are new and advanced ways of accessing large collections of data from diverse sources, such as the Internet.
- The described embodiments of the present invention provide a methodology and system for storing annotations of facts stored in a repository in association with objects. The fact repository includes a large collection of facts, each of which is associated with an object, such as a person, place, book, movie, country, or any other entity of interest. Each fact comprises an attribute, which is descriptive of the type of fact (e.g., “name,” or “population”) and a value for that attribute (e.g., “George Washington”, or “1,397,264,580”). A value can also contain any amount of text—from a single term or phrase to many paragraphs or pages—such as appropriate to describe the attribute. Each object will have a name fact that is the name of the object. The value can include one or more phrases that are themselves the names of other facts.
- In one embodiment, annotations are stored corresponding to some of the facts in the repository. Some annotations, for example, represent number values in the facts, while other annotation values represent dates, geographic locations, ISBN values, names, units, and so on.
- Annotations are passed to requesting objects in response to queries and are used to determine search results Annotations are also used to decide whether facts match and whether facts contain reasonable values.
-
FIG. 1 shows a system architecture, in accordance with an embodiment of the invention. -
FIGS. 2( a)-2(d) are block diagrams illustrating a data structure for facts within a repository ofFIG. 1 in accordance with preferred embodiments of the invention. -
FIG. 2( e) is a block diagram illustrating an alternate data structure for facts and objects in accordance with preferred embodiments of the invention. -
FIG. 2( f) shows a plurality of annotations associated with facts in a repository. -
FIG. 2( g) shows an example of two facts and an associated annotation of one of the facts. -
FIGS. 3( a)-3(c) are flow charts showing methods of creating and using annotations. -
FIG. 4 is a block diagram showing annotation creation. -
FIG. 5 is a flow chart showing annotation creation. -
FIG. 6 shows an example of an XML feed sent in response to a request from on object requester and including annotations. - The figures depict a preferred embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
-
FIG. 1 shows asystem architecture 100 adapted to support one embodiment of the invention.FIG. 1 shows components used to add facts into, and retrieve facts from arepository 115. Thesystem architecture 100 includes anetwork 104, through which any number ofdocument hosts 102 communicate with adata processing system 106, along with any number ofobject requesters - Document hosts 102 store documents and provide access to documents. A document is comprised of any machine-readable data including any combination of text, graphics, multimedia content, etc. A document may be encoded in a markup language, such as Hypertext Markup Language (HTML), i.e., a web page, in an interpreted language (e.g., JavaScript) or in any other computer readable or executable format. A document can include one or more hyperlinks to other documents. A typical document will include one or more facts within its content. A document stored in a
document host 102 may be located and/or identified by a Uniform Resource Locator (URL), or Web address, or any other appropriate form of identification and/or location. Adocument host 102 is implemented by a computer system, and typically includes a server adapted to communicate over thenetwork 104 via networking protocols (e.g., TCP/IP), as well as application and presentation protocols (e.g., HTTP, HTML, SOAP, D-HTML, Java). The documents stored by ahost 102 are typically held in a file directory, a database, or other data repository. Ahost 102 can be implemented in any computing device (e.g., from a PDA or personal computer, a workstation, mini-computer, or mainframe, to a cluster or grid of computers), as well as in any processor architecture or operating system. -
FIG. 1 shows components used to manage facts in afact repository 115.Data processing system 106 includes one ormore importers 108, one ormore janitors 110, abuild engine 112, aservice engine 114, and a fact repository 115 (also called simply a “repository”). Each of the foregoing are implemented, in one embodiment, as software modules (or programs) executed byprocessor 116.Importers 108 operate to process documents received from the document hosts, read the data content of documents, and extract facts (as operationally and programmatically defined within the data processing system 106) from such documents. Theimporters 108 also determine the subject or subjects with which the facts are associated, and extract such facts into individual items of data, for storage in thefact repository 115. In one embodiment, there are different types ofimporters 108 for different types of documents, for example, dependent on the format or document type. -
Janitors 110 operate to process facts extracted byimporter 108. This processing can include but is not limited to, data cleansing, object merging, and fact induction. In one embodiment, there are a number ofdifferent janitors 110 that perform different types of data management operations on the facts. For example, onejanitor 110 may traverse some set of facts in therepository 115 to find duplicate facts (that is, facts that convey the same factual information) and merge them. Anotherjanitor 110 may also normalize facts into standard formats. Anotherjanitor 110 may also remove unwanted facts fromrepository 115, such as facts related to pornographic content. Other types ofjanitors 110 may be implemented, depending on the types of data management functions desired, such as translation, compression, spelling or grammar correction, and the like. -
Various janitors 110 act on facts to normalize attribute names, and values and delete duplicate and near-duplicate facts so an object does not have redundant information. For example, we might find on one page that Britney Spears's birthday is “12/2/1981” while on another page that her date of birth is “Dec. 2, 1981.” Birthday and Date of Birth might both be rewritten as Birthdate by one janitor and then another janitor might notice that 12/2/1981 and Dec. 2, 1981 are different forms of the same date. It would choose the preferred form, remove the other fact and combine the source lists for the two facts. As a result when you look at the source pages for this fact, on some you'll find an exact match of the fact and on others text that is considered to be synonymous with the fact. -
Build engine 112 builds and manages therepository 115.Service engine 114 is an interface for querying therepository 115.Service engine 114's main function is to process queries, score matching objects, and return them to the caller but it is also used byjanitor 110. -
Repository 115 stores factual information extracted from a plurality of documents that are located on document hosts 102. A document from which a particular fact may be extracted is a source document (or “source”) of that particular fact. In other words, a source of a fact includes that fact (or a synonymous fact) within its contents. -
Repository 115 contains one or more facts. In one embodiment, each fact is associated with exactly one object. One implementation for this association includes in each fact an object ID that uniquely identifies the object of the association. In this manner, any number of facts may be associated with an individual object, by including the object ID for that object in the facts. In one embodiment, objects themselves are not physically stored in therepository 115, but rather are defined by the set or group of facts with the same associated object ID, as described below. Further details about facts inrepository 115 are described below, in relation toFIGS. 2( a)-2(d). - It should be appreciated that in practice at least some of the components of the
data processing system 106 will be distributed over multiple computers, communicating over a network. For example,repository 115 may be deployed over multiple servers. As another example, thejanitors 110 may be located on any number of different computers. For convenience of explanation, however, the components of thedata processing system 106 are discussed as though they were implemented on a single computer. - In another embodiment, some or all of document hosts 102 are located on
data processing system 106 instead of being coupled todata processing system 106 by a network. For example,importer 108 may import facts from a database that is a part of or associated withdata processing system 106. -
FIG. 1 also includes components to accessrepository 115 on behalf of one ormore object requesters repository 115.Object requesters system 106, and can be implemented in any computer device or architecture. As shown inFIG. 1 , afirst object requester 152 is located remotely fromsystem 106, while asecond object requester 154 is located indata processing system 106. For example, in a computer system hosting a blog, the blog may include a reference to an object whose facts are inrepository 115. An object requester 152, such as a browser displaying the blog will accessdata processing system 106 so that the information of the facts associated with the object can be displayed as part of the blog web page. As a second example,janitor 110 or other entity considered to be part ofdata processing system 106 can function as object requester 154, requesting the facts of objects fromrepository 115. -
FIG. 1 shows thatdata processing system 106 includes amemory 107 and one ormore processors 116.Memory 107 includesimporters 108,janitors 110, buildengine 112,service engine 114, andrequester 154, each of which are preferably implemented as instructions stored inmemory 107 and executable byprocessor 116.Memory 107 also includesrepository 115.Repository 115 can be stored in a memory of one or more computer systems or in a type of memory such as a disk.FIG. 1 also includes a computerreadable medium 118 containing, for example, at least one ofimporters 108,janitors 110, buildengine 112,service engine 114,requester 154, and at least some portions ofrepository 115.FIG. 1 also includes one or more input/output devices 120 that allow data to be input and output to and fromdata processing system 106. It will be understood thatdata processing system 106 preferably also includes standard software components such as operating systems and the like and further preferably includes standard hardware components not shown in the figure for clarity of example. -
FIG. 2( a) shows an example format of a data structure for facts withinrepository 115, according to some embodiments of the invention. As described above, therepository 115 includesfacts 204. Eachfact 204 includes a unique identifier for that fact, such as afact ID 210. Eachfact 204 includes at least anattribute 212 and avalue 214. For example, a fact associated with an object representing George Washington may include an attribute of “date of birth” and a value of “Feb. 22, 1732.” In one embodiment, all facts are stored as alphanumeric characters since they are extracted from web pages. In another embodiment, facts also can store binary data values. Other embodiments, however, may store fact values as mixed types, or in encoded formats. - As described above, each fact is associated with an
object ID 209 that identifies the object that the fact describes. Thus, each fact that is associated with a same entity (such as George Washington), will have thesame object ID 209. In one embodiment, objects are not stored as separate data entities in memory. In this embodiment, the facts associated with an object contain the same object ID, but no physical object exists. In another embodiment, objects are stored as data entities in memory, and include references (for example, pointers or IDs) to the facts associated with the object. The logical data structure of a fact can take various forms; in general, a fact is represented by a tuple that includes a fact ID, an attribute, a value, and an object ID. The storage implementation of a fact can be in any underlying physical data structure. -
FIG. 2( b) shows an example of facts having respective fact IDs of 10, 20, and 30 inrepository 115.Facts Fact 10 has an attribute of “Name” and a value of “China.”Fact 20 has an attribute of “Category” and a value of “Country.” Thus, the object identified by object ID “1” has aname fact 205 with a value of “China” and acategory fact 206 with a value of “Country.”Fact 30 208 has an attribute of “Property” and a value of “Bill Clinton was the 42nd President of the United States from 1993 to 2001.” Thus, the object identified by object ID “2” has a property fact with a fact ID of 30 and a value of “Bill Clinton was the 42nd President of the United States from 1993 to 2001.”In the illustrated embodiment, each fact has one attribute and one value. The number of facts associated with an object is not limited; thus while only two facts are shown for the “China” object, in practice there may be dozens, even hundreds of facts associated with a given object. Also, the value fields of a fact need not be limited in size or content. For example, a fact about the economy of “China” with an attribute of “Economy” would have a value including several paragraphs of text, numbers, perhaps even tables of figures. This content can be formatted, for example, in a markup language. For example, a fact having an attribute “original html” might have a value of the original html text taken from the source web page. - Also, while the illustration of
FIG. 2( b) shows the explicit coding of object ID, fact ID, attribute, and value, in practice the content of the fact can be implicitly coded as well (e.g., the first field being the object ID, the second field being the fact ID, the third field being the attribute, and the fourth field being the value). Other fields include but are not limited to: the language used to state the fact (English, etc.), how important the fact is, the source of the fact, a confidence value for the fact, and so on. -
FIG. 2( c) shows an example object reference table 210 that is used in some embodiments. Not all embodiments include an object reference table. The object reference table 210 functions to efficiently maintain the associations between object IDs and fact IDs. In the absence of an object reference table 210, it is also possible to find all facts for a given object ID by querying the repository to find all facts with a particular object ID. WhileFIGS. 2( b) and 2(c) illustrate the object reference table 210 with explicit coding of object and fact IDs, the table also may contain just the ID values themselves in column or pair-wise arrangements. -
FIG. 2( d) shows an example of a data structure for facts withinrepository 115, according to some embodiments of the invention showing an extended format of facts. In this example, the fields include anobject reference link 216 to another object. Theobject reference link 216 can be an object ID of another object in therepository 115, or a reference to the location (e.g., table row) for the object in the object reference table 210. Theobject reference link 216 allows facts to have as values other objects. For example, for an object “United States,” there may be a fact with the attribute of “president” and the value of “George W. Bush,” with “George W. Bush” being an object having its own facts inrepository 115. In some embodiments, thevalue field 214 stores the name of the linked object and thelink 216 stores the object identifier of the linked object. Thus, this “president” fact would include thevalue 214 of “George W. Bush”, and objectreference link 216 that contains the object ID for the for “George W. Bush” object. In some other embodiments,facts 204 do not include alink field 216 because thevalue 214 of afact 204 may store a link to another object. - Each
fact 204 also may include one ormore metrics 218. A metric provides an indication of the some quality of the fact. In some embodiments, the metrics include a confidence level and an importance level. The confidence level indicates the likelihood that the fact is correct. The importance level indicates the relevance of the fact to the object, compared to other facts for the same object. The importance level may optionally be viewed as a measure of how vital a fact is to an understanding of the entity or concept represented by the object. - Each
fact 204 includes a list of one ormore sources 220 that include the fact and from which the fact was extracted. Each source may be identified by a Uniform Resource Locator (URL), or Web address, or any other appropriate form of identification and/or location, such as a unique document identifier. - The facts illustrated in
FIG. 2( d) include anagent field 222 that identifies theimporter 108 that extracted the fact. For example, theimporter 108 may be a specialized importer that extracts facts from a specific source (e.g., the pages of a particular web site, or family of web sites) or type of source (e.g., web pages that present factual information in tabular form), or animporter 108 that extracts facts from free text in documents throughout the Web, and so forth. - Some embodiments include one or more specialized facts, such as a
name fact 207 and aproperty fact 208. Aname fact 207 is a fact that conveys a name for the entity or concept represented by the object ID. Aname fact 207 includes anattribute 224 of “name” and a value, which is the name of the object. For example, for an object representing the country Spain, a name fact would have the value “Spain.” Aname fact 207, being a special instance of ageneral fact 204, includes the same fields as anyother fact 204; it has an attribute, a value, a fact ID, metrics, sources, etc. Theattribute 224 of aname fact 207 indicates that the fact is a name fact, and the value is the actual name. The name may be a string of characters. An object ID may have one or more associated name facts, as many entities or concepts can have more than one name. For example, an object ID representing Spain may have associated name facts conveying the country's common name “Spain” and the official name “Kingdom of Spain.” As another example, an object ID representing the U.S. Patent and Trademark Office may have associated name facts conveying the agency's acronyms “PTO” and “USPTO” as well as the official name “United States Patent and Trademark Office.” If an object does have more than one associated name fact, one of the name facts may be designated as a primary name and other name facts may be designated as secondary names, either implicitly or explicitly. - A
property fact 208 is a fact that conveys a statement about the entity or concept represented by the object ID. Property facts are generally used for summary information about an object. Aproperty fact 208, being a special instance of ageneral fact 204, also includes the same parameters (such as attribute, value, fact ID, etc.) asother facts 204. Theattribute field 226 of aproperty fact 208 indicates that the fact is a property fact (e.g., attribute is “property”) and the value is a string of text that conveys the statement of interest. For example, for the object ID representing Bill Clinton, the value of a property fact may be the text string “Bill Clinton was the 42nd President of the United States from 1993 to 2001.” Some object IDs may have one or more associated property facts while other objects may have no associated property facts. It should be appreciated that the data structures shown inFIGS. 2( a)-2(d) and described above are merely exemplary. The data structure of therepository 115 may take on other forms. Other fields may be included in facts and some of the fields described above may be omitted. Additionally, each object ID may have additional special facts aside from name facts and property facts, such as facts conveying a type or category (for example, person, place, movie, actor, organization, etc.) for categorizing the entity or concept represented by the object ID. In some embodiments, an object's name(s) and/or properties may be represented by special records that have a different format than the general facts records 204. - As described previously, a collection of facts is associated with an object ID of an object. An object may become a null or empty object when facts are disassociated from the object. A null object can arise in a number of different ways. One type of null object is an object that has had all of its facts (including name facts) removed, leaving no facts associated with its object ID. Another type of null object is an object that has all of its associated facts other than name facts removed, leaving only its name fact(s). Alternatively, the object may be a null object only if all of its associated name facts are removed. A null object represents an entity or concept for which the
data processing system 106 has no factual information and, as far as thedata processing system 106 is concerned, does not exist. In some embodiments, facts of a null object may be left in therepository 115, but have their object ID values cleared (or have their importance to a negative value). However, the facts of the null object are treated as if they were removed from therepository 115. In some other embodiments, facts of null objects are physically removed fromrepository 115. -
FIG. 2( e) is a block diagram illustrating analternate data structure 290 for facts and objects in accordance with preferred embodiments of the invention. In this data structure, anobject 290 contains anobject ID 292 and references or points tofacts 294. Each fact includes afact ID 295, anattribute 297, and avalue 299. In this embodiment, anobject 290 actually exists inmemory 107. - Referring again to
FIG. 1 , the content of the facts in therepository 115 is also indexed inindex 127. Theindex 127 maintains a term index, which maps terms to {object, fact, field, token} tuples, where “field” is, e.g., attribute or value. Theservice engine 114 is adapted to receive keyword queries from clients such as object requestors, and communicates with theindex 127 to retrieve the facts that are relevant to user's search query. For a generic query containing one or more terms, theservice engine 114 assumes the scope is at the object level. Thus, any object with one or more of the query terms somewhere (not necessarily on the same fact) will match the query for purposes of being ranked in the search results. - In one embodiment the ranking (score) of an object is a linear combination of relevance scores for each of the facts. The relevance score for each fact is based on whether the fact includes one or more query terms (a hit) in, for example, one of the attribute, value, or source portion of the fact. Each hit is scored based on the frequency of the term that is hit, with more common terms getting lower scores, and rarer terms getting higher scores (e.g., using a TF-IDF based term weighting model). The fact score is then adjusted based on additional factors. These factors include the appearance of consecutive query terms in a fact, the appearance of consecutive query terms in a fact in the order in which they appear in the query, the appearance of an exact match for the entire query, the appearance of the query terms in the name fact (or other designated fact, e.g., property or category), and the percentage of facts of the object containing at least one query term. Each fact's score is also adjusted by its associated confidence measure and by its importance measure. Since each fact is independently scored, the facts most relevant and important to any individual query can be determined, and selected. In one embodiment, a selected number (e.g., 5) of the top scoring facts is selected for display in response to a query.
- A user interface for browsing the
fact repository 115 is discussed in co-pending U.S. application Ser. No. 11/356,851, entitled “Browseable Fact Repository,” filed Feb. 17, 2006, which is incorporated by reference herein in its entirety. - In a preferred embodiment of the invention, facts can have associated “annotations.” Annotations are subsets of snippets of the fact's value that are used to provide additional information about facts. Often, an annotation has a high confidence level, especially if it has been entered by a human being or somehow otherwise corroborated. For example, the string “New York, N.Y.” can be used to generate a map plot, but an annotation can associate a latitude and longitude with that string and the latitude/longitude can be plotted on a map. As another example, the Britney Spears object has a large number of facts relating to Britney Spears. Annotations exist for such facts as her birthday, wedding anniversary, and birthplace. It is possible to compare annotations of various facts to determine whether a fact has reasonable values. Certain types of information such as numbers, dates, and locations are good candidates for becoming annotations, as discussed in detail below.
-
FIG. 2( f) shows a format of a plurality of annotations associated with facts inrepository 115 in an embodiment of the invention. The Figure shows three types of annotations (although there can be other types of annotations):Number annotations 296,date annotations 297, and GeoPoint (GeoPt)annotations 298. Each annotation has at least a fact ID, a beginning index in the value of the fact with the fact ID, and a length within the value of the fact value. The fact ID identifies which fact the annotation is associated with. The beginning index is an index into the fact's value where the annotation value begins. The length is a length of the annotation value within the fact's value. -
FIG. 2( g) shows an example of two facts and an associated annotation of one of the facts. As an example, if afact 10 has a value of “Britney Spears was born Dec. 2, 1981” a date annotation associated with that fact might have thefact ID 282 offact 10, an index of 284 (because the date starts on character 25, indexed from 1), and alength 286 of 16 (because the date is 16 characters long). (Other embodiments index from 0.) - In one embodiment, each type of fact is stored together (i.e., all the number facts together, etc). In other embodiments, annotation types are not necessarily stored together. In one embodiment, all fact values, including numeric values dates, latitude and longitude are stored in
repository 115 as characters. Some embodiments also store a copy of the annotation value (for example “Dec. 2, 1981”) with the annotation. Other embodiments store a pointer or reference into the appropriate fact to retrieve the annotation value. Other embodiments store the annotations as part of the facts instead of separately. Some embodiments index annotations inindex 127, causing them to be searchable. - As shown in
FIG. 3( a), annotations can be used when “vetting” facts stored inrepository 115. Such an operation might be performed byjanitor 110 or by any appropriate entity. For a fact received for review instep 322,janitor 110 determines 324 whether the fact is duplicated by other facts in the repository. For example, two facts may contain the same information in different formats. For example, a plurality of facts might have annotations that indicate or suggest that string values of “10 million”, “10,000,000”, and “10000000.000” all represent the same value. As another example, a first fact may contain a distance value in metric format, while a second fact might contain the same distance in Imperial format. In some embodiments, comparison of annotations alone is sufficient to determine duplicates. In other embodiments, comparison of annotations is an initial step andjanitors 110 can go on to make more accurate comparisons using the candidates identified by annotations. Thus, annotations can also be used as an initial screening device to find duplicate facts. - For a given fact received in
step 324,janitor 110 can also use annotations to determine 326 whether the fact has a reasonable value. For example, if there exists an annotation for Britney Spears's birthplace stating that it is “Louisiana”, thenjanitor 110 may use that information to vet the large numbers of facts associated with the Britney Spears object. The Britney Spears's birthplace annotation may have been automatically generated or it may have been hand-entered and vetted by a human being (the latter presumably being more trustworthy). For example, because Louisiana is abbreviated as “LA,” some facts associated with the Britney Spears object may mistakenly contain the value that Britney Spears was born in Los Angeles, which also is sometimes abbreviated as “LA.”Janitor 110 can determine that the facts with a birthplace of Los Angeles” do not match the annotation and choose to remove (or not to store) those facts from therepository 115. - Similarly, the service engine can use annotations to determine which facts to send in response to a query. Facts having values in accordance with corresponding annotation values are given preference.
-
FIGS. 3( b) and 3(c) are flow charts showing additional methods of using annotations.FIG. 3( b) shows an method where a query is received 352 (for example by object service 114). The object service determines 354 a plurality of facts that match the query. Then the object service determines 356 one or more facts that correspond to the determined facts and returns 358 the facts and the annotations. Thus, if the query is “Britney Spears”object service 114 would determine that the facts ofFIG. 2( g) match and would also determine that the annotation ofFIG. 2( g) matches since it corresponds to facts that match the query. In this method, annotations are returned in addition to facts because they provide a fast way to locate pertinent data in the facts without a real-time search of the fact values. -
FIG. 3( c) is a flow chart showing use of annotations to help select facts. A query is received 362 (for example by object service 114). The object service determines 366 a plurality of annotations that are relevant to the query. Relevance of annotations can be determined, for example, by accessing theindex 127 if annotations are indexed, by accessing a separate annotation index (not shown) if annotations are separately indexed, by searching the values of the annotations, or by any other appropriate method. Then the object service determines 366 one or more facts that correspond to the determined annotations and returns 368 the facts. In some embodiments, the annotations are also returned. Thus, if the query is “Britney Spears's birthday”object service 114 would determine that the annotation ofFIG. 2( g) matches and would also determine thatfact 10 is associated with that annotation. Some embodiments would return onlyfact 10. Other embodiments would returnfact 10 and other facts of the “Britney Spears” object that is associated withfact 10. Some embodiments may also return the annotation itself. In this method, annotations are used because they provide a fast way to locate pertinent data in the facts without a real-time search through the fact values. - Annotations can also be used by
service engine 114 to identify erroneous facts that do not match annotation values. -
FIG. 4 is a block diagram showing one method of annotation creation.FIG. 5 is a flow chart showing annotation creation. - A
recognizer 402 is preferably implemented as a software program or hardware device. It examines 504 facts inrepository 115 to extract annotation values. Recognizers may recognize, for example, dates, numbers, locations (which are used to create GeoPt annotations), distances, directions, ISBN numbers, names of persons, measurements, height, weight, mass, volume, and so on. As another example, measurements can be annotated to include units such as “10 meters”, “100 degrees Fahrenheit, and so on. Extracted annotations are encoded in one or more appropriately sized annotation blocks 506 as shown inFIG. 2( f) with a fact ID, index, and length. In some embodiments, the annotation blocks are compacted 508 before being stored 510 inrepository 115 or other appropriate storage. In other embodiments, annotations are added by human beings. In other embodiments, some annotations are added by human beings and some are automatically generated. In some embodiments, annotations added by human beings are given a higher confidence value than annotations that are automatically created. - As discussed above, annotations can be returned in response to a query. This query can be, for example, a browser-based query, in which case, the annotations are returned with the query results. The annotations can be mixed in with the query results or can be displayed separately. For example, annotations can be displayed separately at the top of a results web page.
- Queries can also take the form of requests for XML feeds or other formats of data feeds.
FIG. 6 shows an example of anpartial entry 600 in an XML feed 306 sent in response to a request from object requester 152 (for example, the request: http://google.com/ref/api/q=china). This example is presented partly to show examples of some kinds of annotations and their values. - In the example, an entry corresponds to an object and each atom corresponds to a fact in the object. An object can have more than one associated fact. This example uses the Atom format, although any appropriate feed format can be used.
- In the described embodiment, each object has an associated object ID 601 (in this example “1a27a12f0de4b506a93022496b370c40”). The feed includes a plurality of
facts Fact 602 shows an example of a fact having an attribute and an attribute value, along with a link representing a source of the fact. - Note that, in certain embodiments, for facts associated with an object to be returned in response to a query, only one fact needs to match the query. Thus, in the example, the q parameter is “q=China”.
Fact 602 has a fact with a value containing the string “China”.Facts fact 602. - Some embodiments return partial facts as well as or in addition to complete facts. For example, a query for the date of birth attribute for object number 2038472038 might just return “Jun. 17, 1974” and no other facts for that object.
-
Fact 604 also includes an attribute and a value, and further includes an annotation. In one embodiment, an annotation is associated with a fact inrepository 115. - In
FIG. 6 , the feed forfact 604 has an attribute and a value: -
- attribute=“Population” value=“1306313812 (July 2005 est.)”
- The feed for
fact 604 also has a source link: -
- <atom:link href=“http://www.cia.gov”/>
- The feed for
fact 604 also has two associated annotations: -
<g:annotation begin=“0” length=“10”> <g:number value=“1306313812” /> </g:annotation> <g:annotation begin=“12” length=“9”> <g:date value=“July 2005” /> </g:annotation> - In this embodiment, each annotation has a beginning index, a length, and a value. One of the annotations is a number annotation with a value of “1306313812”. The other annotation is a date annotation with a value of “July 2005”. In some embodiments, a date annotation has separate fields for month, day, and year.
- In the feed for
fact 606 has an associated geopoint annotation: -
</g:annotation> <g:annotation begin=“28” length=“39”> <g:geoPt lat=“38.936283” lon=2“−77.05994” /> </g: annotation> - A geopoint annotation represents a latitude and longitude associated with a fact. Geopoint annotations are noteworthy at least because they contain a two-part value (latitude and longitude). Other types of annotations can have two-or-more-part values as well. Note that in this example, the latitude and longitude values themselves do not appear in the fact. Instead, the value “Washington, District of Columbia, 20008” appears. At some point, an annotation was created for the latitude and longitude of Washington, D.C. and stored in association with that fact (and most likely with all other facts containing a mention of “Washington, D.C.”).
- It will be understood that other types of annotations can be used in the present invention, including but not limited to: name annotations, isbn annotations, units (to indicate a unit for numerical values).
- As discussed above, the feed received by an object requester can be used in a number of ways, including but not limited to display and calculation.
- Some embodiments also support an “alt” parameter, which allows the user to specify the format of the results. It has three possible values: “atom” (the default), “rss”, “osrss”.
-
- /alt=atom/q=albert+einstein
- results for the query “albert einstein” returned in Atom format
- /alt=rss/q=albert+einstein
- results for the query “albert einstein” returned in RSS format
- /alt=osrss/q=albert+einstein
- results for the query “albert einstein” returned in OpenSearch format
- The alt parameter can be combined with the various other parameters:
- /max-facts=5/alt=rss/max-sources=4/q=albert+einstein?start-index=10 five facts per object, four sources per fact, starting at the 10th result, in RSS format.
- The present invention has been described in particular detail with respect to one possible embodiment. Those of skill in the art will appreciate that the invention may be practiced in other embodiments. First, the particular naming of the components, capitalization of terms, the attributes, data structures, or any other programming or structural aspect is not mandatory or significant, and the mechanisms that implement the invention or its features may have different names, formats, or protocols. Further, the system may be implemented via a combination of hardware and software, as described, or entirely in hardware elements. Also, the particular division of functionality between the various system components described herein is merely exemplary, and not mandatory; functions performed by a single system component may instead be performed by multiple components, and functions performed by multiple components may instead performed by a single component.
- Some portions of above description present the features of the present invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. These operations, while described functionally or logically, are understood to be implemented by computer programs. Furthermore, it has also proven convenient at times, to refer to these arrangements of operations as modules or by functional names, without loss of generality.
- Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- Certain aspects of the present invention include process steps and instructions described herein in the form of an algorithm. It should be noted that the process steps and instructions of the present invention could be embodied in software, firmware or hardware, and when embodied in software, could be downloaded to reside on and be operated from different platforms used by real time network operating systems.
- The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored on a computer readable medium that can be accessed by the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, application specific integrated circuits (ASICs), or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus. Furthermore, the computers referred to in the specification may include a single processor or may be architectures employing multiple processor designs for increased computing capability.
- The algorithms and operations presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may also be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will be apparent to those of skill in the, along with equivalent variations. In addition, the present invention is not described with reference to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references to specific languages are provided for disclosure of enablement and best mode of the present invention.
- The present invention is well suited to a wide variety of computer network systems over numerous topologies. Within this field, the configuration and management of large networks comprise storage devices and computers that are communicatively coupled to dissimilar computers and storage devices over a network, such as the Internet.
- Finally, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.
Claims (1)
1. A method of creating annotations for facts in a fact repository, performed at a computer system having one or more processors and memory storing one or more programs for execution by the one or more processors, comprising:
processing a fact in a fact repository, the fact having a fact attribute and a fact value, to determine a corresponding value for an annotation, wherein the annotation includes additional information about the fact, wherein the annotation is directed to a subset of the fact value, wherein the fact repository includes a plurality of facts associated with objects, wherein a respective fact in the fact repository includes a respective fact attribute and a respective fact value, wherein the respective fact value is a text string, and wherein the plurality of facts is extracted from a plurality of documents; and
storing the corresponding value as an annotation value in the fact repository, wherein the annotation value is indexed to a substring of the fact value.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/292,030 US20120117077A1 (en) | 2006-02-17 | 2011-11-08 | Annotation Framework |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/356,728 US8055674B2 (en) | 2006-02-17 | 2006-02-17 | Annotation framework |
US13/292,030 US20120117077A1 (en) | 2006-02-17 | 2011-11-08 | Annotation Framework |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/356,728 Division US8055674B2 (en) | 2006-01-27 | 2006-02-17 | Annotation framework |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120117077A1 true US20120117077A1 (en) | 2012-05-10 |
Family
ID=38429574
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/356,728 Active 2026-12-10 US8055674B2 (en) | 2006-01-27 | 2006-02-17 | Annotation framework |
US13/292,017 Abandoned US20120124053A1 (en) | 2006-02-17 | 2011-11-08 | Annotation Framework |
US13/292,030 Abandoned US20120117077A1 (en) | 2006-02-17 | 2011-11-08 | Annotation Framework |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/356,728 Active 2026-12-10 US8055674B2 (en) | 2006-01-27 | 2006-02-17 | Annotation framework |
US13/292,017 Abandoned US20120124053A1 (en) | 2006-02-17 | 2011-11-08 | Annotation Framework |
Country Status (1)
Country | Link |
---|---|
US (3) | US8055674B2 (en) |
Families Citing this family (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8185564B1 (en) * | 2006-11-21 | 2012-05-22 | Google Inc. | Redirection of embedded content |
US9141687B2 (en) * | 2008-01-03 | 2015-09-22 | Hewlett-Packard Development Company, L.P. | Identification of data objects within a computer database |
US20090217149A1 (en) * | 2008-02-08 | 2009-08-27 | Mind-Alliance Systems, Llc. | User Extensible Form-Based Data Association Apparatus |
US8199166B2 (en) * | 2008-03-14 | 2012-06-12 | Schlumberger Technology Corporation | Visualization techniques for oilfield operations |
FR2930660A1 (en) * | 2008-04-25 | 2009-10-30 | Canon Kk | METHOD FOR ACCESSING A PART OR MODIFYING A PART OF A BINARY XML DOCUMENT, ASSOCIATED DEVICES |
US8645391B1 (en) | 2008-07-03 | 2014-02-04 | Google Inc. | Attribute-value extraction from structured documents |
US8434134B2 (en) | 2010-05-26 | 2013-04-30 | Google Inc. | Providing an electronic document collection |
US8856640B1 (en) | 2012-01-20 | 2014-10-07 | Google Inc. | Method and apparatus for applying revision specific electronic signatures to an electronically stored document |
US9864482B2 (en) * | 2012-03-13 | 2018-01-09 | Cognilore Inc. | Method of navigating through digital content |
US9086943B2 (en) * | 2012-06-13 | 2015-07-21 | International Business Machines Corporation | Integrated development environment-based repository searching in a networked computing environment |
US20130339001A1 (en) * | 2012-06-19 | 2013-12-19 | Microsoft Corporation | Spelling candidate generation |
US9870554B1 (en) | 2012-10-23 | 2018-01-16 | Google Inc. | Managing documents based on a user's calendar |
US11308037B2 (en) | 2012-10-30 | 2022-04-19 | Google Llc | Automatic collaboration |
US9529916B1 (en) | 2012-10-30 | 2016-12-27 | Google Inc. | Managing documents based on access context |
US9384285B1 (en) | 2012-12-18 | 2016-07-05 | Google Inc. | Methods for identifying related documents |
US9495341B1 (en) | 2012-12-18 | 2016-11-15 | Google Inc. | Fact correction and completion during document drafting |
US10235358B2 (en) * | 2013-02-21 | 2019-03-19 | Microsoft Technology Licensing, Llc | Exploiting structured content for unsupervised natural language semantic parsing |
US9514113B1 (en) | 2013-07-29 | 2016-12-06 | Google Inc. | Methods for automatic footnote generation |
US9842113B1 (en) | 2013-08-27 | 2017-12-12 | Google Inc. | Context-based file selection |
US9529791B1 (en) | 2013-12-12 | 2016-12-27 | Google Inc. | Template and content aware document and template editing |
US10073840B2 (en) | 2013-12-20 | 2018-09-11 | Microsoft Technology Licensing, Llc | Unsupervised relation detection model training |
US9870356B2 (en) | 2014-02-13 | 2018-01-16 | Microsoft Technology Licensing, Llc | Techniques for inferring the unknown intents of linguistic items |
US9703763B1 (en) | 2014-08-14 | 2017-07-11 | Google Inc. | Automatic document citations by utilizing copied content for candidate sources |
US9824385B2 (en) | 2014-12-29 | 2017-11-21 | Ebay Inc. | Method for performing sequence labelling on queries |
US10452661B2 (en) | 2015-06-18 | 2019-10-22 | Microsoft Technology Licensing, Llc | Automated database schema annotation |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5010478A (en) * | 1986-04-11 | 1991-04-23 | Deran Roger L | Entity-attribute value database system with inverse attribute for selectively relating two different entities |
US5664109A (en) * | 1995-06-07 | 1997-09-02 | E-Systems, Inc. | Method for extracting pre-defined data items from medical service records generated by health care providers |
US5815415A (en) * | 1996-01-19 | 1998-09-29 | Bentley Systems, Incorporated | Computer system for portable persistent modeling |
US6249784B1 (en) * | 1999-05-19 | 2001-06-19 | Nanogen, Inc. | System and method for searching and processing databases comprising named annotated text strings |
US6311189B1 (en) * | 1998-03-11 | 2001-10-30 | Altavista Company | Technique for matching a query to a portion of media |
US20030046288A1 (en) * | 2001-08-31 | 2003-03-06 | Severino Donna M. | Method and apparatus for data storage and retrieval |
US20040122846A1 (en) * | 2002-12-19 | 2004-06-24 | Ibm Corporation | Fact verification system |
US20040260714A1 (en) * | 2003-06-20 | 2004-12-23 | Avijit Chatterjee | Universal annotation management system |
US20050086222A1 (en) * | 2003-10-16 | 2005-04-21 | Wang Ji H. | Semi-automatic construction method for knowledge base of encyclopedia question answering system |
US20050108630A1 (en) * | 2003-11-19 | 2005-05-19 | Wasson Mark D. | Extraction of facts from text |
US20060112110A1 (en) * | 2004-11-23 | 2006-05-25 | International Business Machines Corporation | System and method for automating data normalization using text analytics |
US20070055656A1 (en) * | 2005-08-01 | 2007-03-08 | Semscript Ltd. | Knowledge repository |
Family Cites Families (130)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4888690A (en) | 1985-01-11 | 1989-12-19 | Wang Laboratories, Inc. | Interactive error handling means in database management |
US4899292A (en) | 1988-03-02 | 1990-02-06 | Image Storage/Retrieval Systems, Inc. | System for storing and retrieving text and associated graphics |
CA2048306A1 (en) | 1990-10-02 | 1992-04-03 | Steven P. Miller | Distributed configuration profile for computing system |
US5649183A (en) | 1992-12-08 | 1997-07-15 | Microsoft Corporation | Method for compressing full text indexes with document identifiers and location offsets |
US5574898A (en) | 1993-01-08 | 1996-11-12 | Atria Software, Inc. | Dynamic software version auditor which monitors a process to provide a list of objects that are accessed |
US5544051A (en) * | 1993-09-17 | 1996-08-06 | Digital Equipment Corporation | Document management system using multiple threaded processes and having asynchronous repository responses and no busy cursor |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US6216138B1 (en) | 1994-04-22 | 2001-04-10 | Brooks Automation Inc. | Computer interface system for automatically generating graphical representations of computer operations linked together according to functional relationships |
US6029195A (en) | 1994-11-29 | 2000-02-22 | Herz; Frederick S. M. | System for customized electronic identification of desirable objects |
US5963940A (en) | 1995-08-16 | 1999-10-05 | Syracuse University | Natural language information retrieval system and method |
US6026388A (en) | 1995-08-16 | 2000-02-15 | Textwise, Llc | User interface and other enhancements for natural language information retrieval system and method |
US6006221A (en) | 1995-08-16 | 1999-12-21 | Syracuse University | Multilingual document retrieval system and method using semantic vector matching |
US6076088A (en) | 1996-02-09 | 2000-06-13 | Paik; Woojin | Information extraction system and method using concept relation concept (CRC) triples |
US5778378A (en) | 1996-04-30 | 1998-07-07 | International Business Machines Corporation | Object oriented information retrieval framework mechanism |
US6014661A (en) | 1996-05-06 | 2000-01-11 | Ivee Development Ab | System and method for automatic analysis of data bases and for user-controlled dynamic querying |
US6101515A (en) | 1996-05-31 | 2000-08-08 | Oracle Corporation | Learning system for classification of terminology |
US5870739A (en) * | 1996-09-20 | 1999-02-09 | Novell, Inc. | Hybrid query apparatus and method |
JP3099756B2 (en) * | 1996-10-31 | 2000-10-16 | 富士ゼロックス株式会社 | Document processing device, word extraction device, and word extraction method |
US6480194B1 (en) | 1996-11-12 | 2002-11-12 | Silicon Graphics, Inc. | Computer-related method, system, and program product for controlling data visualization in external dimension(s) |
US6498921B1 (en) | 1999-09-01 | 2002-12-24 | Chi Fai Ho | Method and system to answer a natural-language question |
US5966126A (en) | 1996-12-23 | 1999-10-12 | Szabo; Andrew J. | Graphic user interface for database system |
US5946692A (en) | 1997-05-08 | 1999-08-31 | At & T Corp | Compressed representation of a data base that permits AD HOC querying |
CA2242158C (en) * | 1997-07-01 | 2004-06-01 | Hitachi, Ltd. | Method and apparatus for searching and displaying structured document |
US5987448A (en) | 1997-07-25 | 1999-11-16 | Claritech Corporation | Methodology for displaying search results using character recognition |
US6188403B1 (en) | 1997-11-21 | 2001-02-13 | Portola Dimensional Systems, Inc. | User-friendly graphics generator using direct manipulation |
US6105030A (en) | 1998-02-27 | 2000-08-15 | Oracle Corporation | Method and apparatus for copying data that resides in a database |
US6327574B1 (en) | 1998-07-07 | 2001-12-04 | Encirq Corporation | Hierarchical models of consumer attributes for targeting content in a privacy-preserving manner |
US6529900B1 (en) | 1999-01-14 | 2003-03-04 | International Business Machines Corporation | Method and apparatus for data visualization |
US6377943B1 (en) | 1999-01-20 | 2002-04-23 | Oracle Corp. | Initial ordering of tables for database queries |
GB9903451D0 (en) | 1999-02-16 | 1999-04-07 | Hewlett Packard Co | Similarity searching for documents |
US6584464B1 (en) | 1999-03-19 | 2003-06-24 | Ask Jeeves, Inc. | Grammar template query system |
US6263328B1 (en) | 1999-04-09 | 2001-07-17 | International Business Machines Corporation | Object oriented query model and process for complex heterogeneous database queries |
US20030195872A1 (en) | 1999-04-12 | 2003-10-16 | Paul Senn | Web-based information content analyzer and information dimension dictionary |
US6304864B1 (en) | 1999-04-20 | 2001-10-16 | Textwise Llc | System for retrieving multimedia information from the internet using multiple evolving intelligent agents |
US6629097B1 (en) | 1999-04-28 | 2003-09-30 | Douglas K. Keith | Displaying implicit associations among items in loosely-structured data sets |
US6721713B1 (en) | 1999-05-27 | 2004-04-13 | Andersen Consulting Llp | Business alliance identification in a web architecture framework |
EP1058236B1 (en) | 1999-05-31 | 2007-03-07 | Nippon Telegraph and Telephone Corporation | Speech recognition based database query system |
US6873982B1 (en) | 1999-07-16 | 2005-03-29 | International Business Machines Corporation | Ordering of database search results based on user feedback |
US6341306B1 (en) | 1999-08-13 | 2002-01-22 | Atomica Corporation | Web-based information retrieval responsive to displayed word identified by a text-grabbing algorithm |
CA2281331A1 (en) | 1999-09-03 | 2001-03-03 | Cognos Incorporated | Database management system |
US6105020A (en) | 1999-10-11 | 2000-08-15 | International Business Machines Corporation | System and method for identifying and constructing star joins for execution by bitmap ANDing |
US6519603B1 (en) * | 1999-10-28 | 2003-02-11 | International Business Machine Corporation | Method and system for organizing an annotation structure and for querying data and annotations |
US6850896B1 (en) | 1999-10-28 | 2005-02-01 | Market-Touch Corporation | Method and system for managing and providing sales data using world wide web |
JP3888812B2 (en) * | 1999-11-01 | 2007-03-07 | 富士通株式会社 | Fact data integration method and apparatus |
US6546388B1 (en) | 2000-01-14 | 2003-04-08 | International Business Machines Corporation | Metadata search results ranking system |
US6606659B1 (en) | 2000-01-28 | 2003-08-12 | Websense, Inc. | System and method for controlling access to internet sites |
US20030120659A1 (en) | 2000-03-20 | 2003-06-26 | Sridhar Mandayam Anandampillai | Systems for developing websites and methods therefor |
US6643641B1 (en) | 2000-04-27 | 2003-11-04 | Russell Snyder | Web search engine with graphic snapshots |
US7325201B2 (en) * | 2000-05-18 | 2008-01-29 | Endeca Technologies, Inc. | System and method for manipulating content in a hierarchical data-driven search and navigation system |
US7401131B2 (en) | 2000-05-22 | 2008-07-15 | Verizon Business Global Llc | Method and system for implementing improved containers in a global ecosystem of interrelated services |
US6754677B1 (en) | 2000-05-30 | 2004-06-22 | Outlooksoft Corporation | Method and system for facilitating information exchange |
US7328349B2 (en) | 2001-12-14 | 2008-02-05 | Bbn Technologies Corp. | Hash-based systems and methods for detecting, preventing, and tracing network worms and viruses |
US7640489B2 (en) | 2000-08-01 | 2009-12-29 | Sun Microsystems, Inc. | Methods and systems for inputting data into spreadsheet documents |
US20020049738A1 (en) * | 2000-08-03 | 2002-04-25 | Epstein Bruce A. | Information collaboration and reliability assessment |
US7100083B2 (en) | 2000-08-04 | 2006-08-29 | Sun Microsystems, Inc. | Checks for product knowledge management |
US20030217052A1 (en) | 2000-08-24 | 2003-11-20 | Celebros Ltd. | Search engine method and apparatus |
AU2001290597A1 (en) | 2000-09-01 | 2002-03-13 | Togethersoft Corporation | Methods and systems for optimizing resource allocation based on data mined from plans created from a workflow |
US6832218B1 (en) | 2000-09-22 | 2004-12-14 | International Business Machines Corporation | System and method for associating search results |
US20020065815A1 (en) | 2000-10-04 | 2002-05-30 | Xcelerix, Inc. | Systems and methods for searching a database |
US7013308B1 (en) | 2000-11-28 | 2006-03-14 | Semscript Ltd. | Knowledge storage and retrieval system and method |
US6781599B2 (en) | 2001-01-04 | 2004-08-24 | At&T | System and method for visualizing massive multi-digraphs |
US6920477B2 (en) | 2001-04-06 | 2005-07-19 | President And Fellows Of Harvard College | Distributed, compressed Bloom filter Web cache server |
US7031955B1 (en) | 2001-04-27 | 2006-04-18 | I2 Technologies Us, Inc. | Optimization using a multi-dimensional data model |
US6961723B2 (en) | 2001-05-04 | 2005-11-01 | Sun Microsystems, Inc. | System and method for determining relevancy of query responses in a distributed network search mechanism |
US7398201B2 (en) | 2001-08-14 | 2008-07-08 | Evri Inc. | Method and system for enhanced data searching |
US7403938B2 (en) | 2001-09-24 | 2008-07-22 | Iac Search & Media, Inc. | Natural language query processing |
US6826572B2 (en) | 2001-11-13 | 2004-11-30 | Overture Services, Inc. | System and method allowing advertisers to manage search listings in a pay for placement search system using grouping |
JP3931214B2 (en) | 2001-12-17 | 2007-06-13 | 日本アイ・ビー・エム株式会社 | Data analysis apparatus and program |
US6988018B2 (en) | 2001-12-26 | 2006-01-17 | Eames John D | System and method for analyzing controlling forming sections of a paper machine in operation |
US20030154071A1 (en) | 2002-02-11 | 2003-08-14 | Shreve Gregory M. | Process for the document management and computer-assisted translation of documents utilizing document corpora constructed by intelligent agents |
US7343365B2 (en) | 2002-02-20 | 2008-03-11 | Microsoft Corporation | Computer system architecture for automatic context associations |
US6928436B2 (en) | 2002-02-28 | 2005-08-09 | Ilog Sa | Interactive generation of graphical visualizations of large data structures |
US7043521B2 (en) | 2002-03-21 | 2006-05-09 | Rockwell Electronic Commerce Technologies, Llc | Search agent for searching the internet |
US20040030731A1 (en) | 2002-04-03 | 2004-02-12 | Liviu Iftode | System and method for accessing files in a network |
US20030208665A1 (en) | 2002-05-01 | 2003-11-06 | Jih-Kwon Peir | Reducing data speculation penalty with early cache hit/miss prediction |
US7158983B2 (en) | 2002-09-23 | 2007-01-02 | Battelle Memorial Institute | Text analysis technique |
DE10245900A1 (en) | 2002-09-30 | 2004-04-08 | Neven jun., Hartmut, Prof.Dr. | Image based query system for search engines or databases of mobile telephone, portable computer uses image recognition to access more information about objects in image |
JP4664076B2 (en) * | 2002-09-30 | 2011-04-06 | キューナチュラリー システムズ インコーポレイテッド | Blinking annotation callouts to highlight cross-language search results |
US20040167910A1 (en) | 2002-12-06 | 2004-08-26 | Attensity Corporation | Integrated data products of processes of integrating mixed format data |
US7181450B2 (en) | 2002-12-18 | 2007-02-20 | International Business Machines Corporation | Method, system, and program for use of metadata to create multidimensional cubes in a relational database |
US7107528B2 (en) * | 2002-12-20 | 2006-09-12 | International Business Machines Corporation | Automatic completion of dates |
US7278111B2 (en) | 2002-12-26 | 2007-10-02 | Yahoo! Inc. | Systems and methods for selecting a date or range of dates |
US7146538B2 (en) * | 2003-03-28 | 2006-12-05 | Hewlett-Packard Development Company, L.P. | Bus interface module |
US8095544B2 (en) * | 2003-05-30 | 2012-01-10 | Dictaphone Corporation | Method, system, and apparatus for validation |
US7111025B2 (en) | 2003-04-30 | 2006-09-19 | International Business Machines Corporation | Information retrieval system and method using index ANDing for improving performance |
US7853508B2 (en) | 2003-05-19 | 2010-12-14 | Serena Software, Inc. | Method and system for object-oriented management of multi-dimensional data |
US7926103B2 (en) | 2003-06-05 | 2011-04-12 | Hewlett-Packard Development Company, L.P. | System and method for preventing replay attacks |
US7836391B2 (en) | 2003-06-10 | 2010-11-16 | Google Inc. | Document search engine including highlighting of confident results |
US9026901B2 (en) | 2003-06-20 | 2015-05-05 | International Business Machines Corporation | Viewing annotations across multiple applications |
US8321470B2 (en) * | 2003-06-20 | 2012-11-27 | International Business Machines Corporation | Heterogeneous multi-level extendable indexing for general purpose annotation systems |
US7162473B2 (en) | 2003-06-26 | 2007-01-09 | Microsoft Corporation | Method and system for usage analyzer that determines user accessed sources, indexes data subsets, and associated metadata, processing implicit queries based on potential interest to users |
US7565425B2 (en) | 2003-07-02 | 2009-07-21 | Amazon Technologies, Inc. | Server architecture and methods for persistently storing and serving event data |
US7814093B2 (en) | 2003-07-25 | 2010-10-12 | Microsoft Corporation | Method and system for building a report for execution against a data store |
US20050027664A1 (en) * | 2003-07-31 | 2005-02-03 | Johnson David E. | Interactive machine learning system for automated annotation of information in text |
US7444515B2 (en) | 2003-08-14 | 2008-10-28 | Washington University | Method and apparatus for detecting predefined signatures in packet payload using Bloom filters |
US7174328B2 (en) | 2003-09-02 | 2007-02-06 | International Business Machines Corp. | Selective path signatures for query processing over a hierarchical tagged data structure |
US7409406B2 (en) | 2003-09-08 | 2008-08-05 | International Business Machines Corporation | Uniform search system and method for selectively sharing distributed access-controlled documents |
US20050057566A1 (en) | 2003-09-11 | 2005-03-17 | International Business Machines Corporation | Rich graphic visualization generation from abstract data representation |
US7236982B2 (en) | 2003-09-15 | 2007-06-26 | Pic Web Services, Inc. | Computer systems and methods for platform independent presentation design |
US7496560B2 (en) | 2003-09-23 | 2009-02-24 | Amazon Technologies, Inc. | Personalized searchable library with highlighting capabilities |
US7620624B2 (en) | 2003-10-17 | 2009-11-17 | Yahoo! Inc. | Systems and methods for indexing content for fast and scalable retrieval |
US20050083413A1 (en) | 2003-10-20 | 2005-04-21 | Logicalis | Method, system, apparatus, and machine-readable medium for use in connection with a server that uses images or audio for initiating remote function calls |
US20050187898A1 (en) | 2004-02-05 | 2005-08-25 | Nec Laboratories America, Inc. | Data Lookup architecture |
US20050216464A1 (en) | 2004-03-27 | 2005-09-29 | Microsoft Corporation | Automated authoring tool and method to facilitate inclusion of maps and other geographical data into travelogues |
US20050219929A1 (en) | 2004-03-30 | 2005-10-06 | Navas Julio C | Method and apparatus achieving memory and transmission overhead reductions in a content routing network |
US20050268212A1 (en) | 2004-05-28 | 2005-12-01 | Michael Dagel | System, apparatus, and method for desktop-based creation and publication of a periodic community newsletter |
US7685112B2 (en) * | 2004-06-17 | 2010-03-23 | The Regents Of The University Of California | Method and apparatus for retrieving and indexing hidden pages |
US8051207B2 (en) | 2004-06-25 | 2011-11-01 | Citrix Systems, Inc. | Inferring server state in s stateless communication protocol |
US7493335B2 (en) | 2004-07-02 | 2009-02-17 | Graphlogic Inc. | Object process graph relational database interface |
US20060020582A1 (en) | 2004-07-22 | 2006-01-26 | International Business Machines Corporation | Method and system for processing abstract derived entities defined in a data abstraction model |
US20060053175A1 (en) * | 2004-09-03 | 2006-03-09 | Biowisdom Limited | System and method for creating, editing, and utilizing one or more rules for multi-relational ontology creation and maintenance |
US7809763B2 (en) | 2004-10-15 | 2010-10-05 | Oracle International Corporation | Method(s) for updating database object metadata |
US20060085386A1 (en) | 2004-10-19 | 2006-04-20 | Microsoft Corporation | Two pass calculation to optimize formula calculations for a spreadsheet |
US20060149700A1 (en) * | 2004-11-11 | 2006-07-06 | Gladish Randolph J | System and method for automatic geospatial web network generation via metadata transformation |
US7464090B2 (en) | 2006-01-27 | 2008-12-09 | Google Inc. | Object categorization for information extraction |
US20060173824A1 (en) | 2005-02-01 | 2006-08-03 | Metalincs Corporation | Electronic communication analysis and visualization |
EP1859378A2 (en) | 2005-03-03 | 2007-11-28 | Washington University | Method and apparatus for performing biosequence similarity searching |
US7587387B2 (en) | 2005-03-31 | 2009-09-08 | Google Inc. | User interface for facts query engine with snippets from information sources that include query terms and answer terms |
US20060248456A1 (en) * | 2005-05-02 | 2006-11-02 | Ibm Corporation | Assigning a publication date for at least one electronic document |
US7809722B2 (en) | 2005-05-09 | 2010-10-05 | Like.Com | System and method for enabling search and retrieval from image files based on recognized information |
US20080005064A1 (en) * | 2005-06-28 | 2008-01-03 | Yahoo! Inc. | Apparatus and method for content annotation and conditional annotation retrieval in a search context |
US20070022085A1 (en) | 2005-07-22 | 2007-01-25 | Parashuram Kulkarni | Techniques for unsupervised web content discovery and automated query generation for crawling the hidden web |
US8726144B2 (en) * | 2005-12-23 | 2014-05-13 | Xerox Corporation | Interactive learning-based document annotation |
US7761436B2 (en) * | 2006-01-03 | 2010-07-20 | Yahoo! Inc. | Apparatus and method for controlling content access based on shared annotations for annotated users in a folksonomy scheme |
US7555471B2 (en) | 2006-01-27 | 2009-06-30 | Google Inc. | Data object visualization |
US20070179965A1 (en) | 2006-01-27 | 2007-08-02 | Hogue Andrew W | Designating data objects for analysis |
US9176984B2 (en) | 2006-07-31 | 2015-11-03 | Ricoh Co., Ltd | Mixed media reality retrieval of differentially-weighted links |
KR100865973B1 (en) | 2007-02-08 | 2008-10-30 | (주)올라웍스 | Method for searching certain person and method and system for generating copyright report for the certain person |
US9058370B2 (en) | 2007-02-27 | 2015-06-16 | International Business Machines Corporation | Method, system and program product for defining imports into and exports out from a database system using spread sheets by use of a control language |
US20080267504A1 (en) | 2007-04-24 | 2008-10-30 | Nokia Corporation | Method, device and computer program product for integrating code-based and optical character recognition technologies into a mobile visual search |
-
2006
- 2006-02-17 US US11/356,728 patent/US8055674B2/en active Active
-
2011
- 2011-11-08 US US13/292,017 patent/US20120124053A1/en not_active Abandoned
- 2011-11-08 US US13/292,030 patent/US20120117077A1/en not_active Abandoned
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5010478A (en) * | 1986-04-11 | 1991-04-23 | Deran Roger L | Entity-attribute value database system with inverse attribute for selectively relating two different entities |
US5664109A (en) * | 1995-06-07 | 1997-09-02 | E-Systems, Inc. | Method for extracting pre-defined data items from medical service records generated by health care providers |
US5815415A (en) * | 1996-01-19 | 1998-09-29 | Bentley Systems, Incorporated | Computer system for portable persistent modeling |
US6311189B1 (en) * | 1998-03-11 | 2001-10-30 | Altavista Company | Technique for matching a query to a portion of media |
US6249784B1 (en) * | 1999-05-19 | 2001-06-19 | Nanogen, Inc. | System and method for searching and processing databases comprising named annotated text strings |
US20030046288A1 (en) * | 2001-08-31 | 2003-03-06 | Severino Donna M. | Method and apparatus for data storage and retrieval |
US20040122846A1 (en) * | 2002-12-19 | 2004-06-24 | Ibm Corporation | Fact verification system |
US20040260714A1 (en) * | 2003-06-20 | 2004-12-23 | Avijit Chatterjee | Universal annotation management system |
US20050086222A1 (en) * | 2003-10-16 | 2005-04-21 | Wang Ji H. | Semi-automatic construction method for knowledge base of encyclopedia question answering system |
US20050108630A1 (en) * | 2003-11-19 | 2005-05-19 | Wasson Mark D. | Extraction of facts from text |
US20060112110A1 (en) * | 2004-11-23 | 2006-05-25 | International Business Machines Corporation | System and method for automating data normalization using text analytics |
US20070055656A1 (en) * | 2005-08-01 | 2007-03-08 | Semscript Ltd. | Knowledge repository |
Also Published As
Publication number | Publication date |
---|---|
US20070198499A1 (en) | 2007-08-23 |
US8055674B2 (en) | 2011-11-08 |
US20120124053A1 (en) | 2012-05-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8055674B2 (en) | Annotation framework | |
US7454398B2 (en) | Support for object search | |
US8954426B2 (en) | Query language | |
US10223406B2 (en) | Entity normalization via name normalization | |
US8260785B2 (en) | Automatic object reference identification and linking in a browseable fact repository | |
US7774328B2 (en) | Browseable fact repository | |
US9558186B2 (en) | Unsupervised extraction of facts | |
US7778952B2 (en) | Displaying facts on a linear graph | |
US9760570B2 (en) | Finding and disambiguating references to entities on web pages | |
US7555471B2 (en) | Data object visualization | |
US7672971B2 (en) | Modular architecture for entity normalization | |
US20070198597A1 (en) | Attribute entropy as a signal in object normalization | |
US7925676B2 (en) | Data object visualization using maps | |
US20140320499A1 (en) | Data object visualization using graphs | |
US20070179965A1 (en) | Designating data objects for analysis | |
US9785686B2 (en) | Corroborating facts in electronic documents |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |