US20120136859A1 - Entity Type Assignment - Google Patents
Entity Type Assignment Download PDFInfo
- Publication number
- US20120136859A1 US20120136859A1 US13/171,296 US201113171296A US2012136859A1 US 20120136859 A1 US20120136859 A1 US 20120136859A1 US 201113171296 A US201113171296 A US 201113171296A US 2012136859 A1 US2012136859 A1 US 2012136859A1
- Authority
- US
- United States
- Prior art keywords
- entity type
- facts
- fact
- entity
- objects
- 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N20/00—Machine learning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/02—Knowledge representation; Symbolic representation
- G06N5/022—Knowledge engineering; Knowledge acquisition
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/04—Inference or reasoning models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N7/00—Computing arrangements based on specific mathematical models
- G06N7/01—Probabilistic graphical models, e.g. probabilistic networks
Definitions
- the disclosed embodiments generally relate to fact databases or repositories. Specifically, the disclosed embodiments relate to methods of learning entity type models from objects in fact repositories and using these models to assign entity types to objects of unknown entity type in the fact repository.
- Computational techniques such as information extraction are used to automatically identify and extract information in the form of facts.
- Information extraction can be performed on a variety of sources such as web pages to extract fact data.
- sources such as web pages to extract fact data.
- a set of facts collected from a source describing the same entity may be organized and can be stored as an object in a repository of facts.
- Facts contain an attribute that describes an entity.
- the entity type of the entity is the type of real world thing the object represents (e.g. Person, Dog, Book, Movie). Entity type can be defined in a fact associated with the object. This entity type information is necessary to understand relationships between sets of facts associated with different objects. For example, an object with entity name “Hillary Clinton” is associated with a fact, “spouse Bill Clinton” and it is known that the attribute “spouse” always has a value with entity type “Person”. Knowing that an object with entity name “Bill Clinton” has an entity type of “Person” enables the identification of a relationship between the two objects.
- entity type is used in association with the attribute defined by the fact to assign a confidence to the fact. For example, an object with entity name “Bill Clinton” has an attribute “genre” with an associated value “political”. If we know “genre” is only is used to describe a closed set of entity types such as “Book” and “Movie”, knowing that “Bill Clinton” is of entity type “Book” can provide a better confidence in that fact.
- entity type information may not be available in the source data. Due to inherent error in information extraction, entity type information may not be extracted.
- entity type of an object may also be confounded by several objects having the same name. For example, an object with entity name “Bill Clinton” could be either an object with entity type “Person” or an object with entity type “Book”.
- Embodiments of the method comprise identifying a plurality of objects derived from electronic documents, each object including one or more facts describing an entity with which the object is associated, wherein each fact comprises an attribute.
- the method generates a set of features describing the facts included with the object for each of the plurality of objects.
- the method further identifies a subset of the plurality of objects of a known entity type.
- the method further generates an entity type model based on the sets of features generated for the objects in the identified subset.
- the method also generates a value based on an object of unknown entity type and the entity type model, wherein the value indicates whether the object of unknown entity type is of the known entity type.
- the method assigns the known entity type to the object of unknown entity type responsive to a determination that the value indicates the object of unknown entity type is of the known entity type and stores the object to which the known entity type was assigned.
- Embodiments of the system and computer program product comprise a repository which stores a plurality of objects derived from electronic documents, each object including one or more facts describing an entity with which the object is associated, wherein each fact comprises an attribute.
- the system and computer program product also comprise a feature generation module adapted to generate, for each of the plurality of objects, a set of features describing the facts included with the object.
- An entity type model module adapted to generate an entity type model based on the sets of features generated for a subset of objects of a known entity type.
- the system and computer product further comprise an entity type model module adapted to generate an entity type model based on the sets of features generated for a subset of objects of a known entity type.
- the system and computer product further comprise an entity type assignment module adapted to generate a value based on an object of unknown entity type and the entity type model, wherein the value indicates whether the object of unknown entity type is of the known entity type.
- an object update module stores the object to which the known entity type was assigned.
- FIG. 1 shows a system architecture adapted to support one embodiment.
- FIGS. 2 ( a )- 2 ( d ) are block diagrams illustrating a data structure for facts within a repository of FIG. 1 in accordance with some embodiments.
- FIG. 2( e ) is a block diagram illustrating an alternate data structure for facts and objects in accordance with some embodiments.
- FIG. 3 is a block diagram illustrating an entity type assignment engine according to one embodiment.
- FIG. 4 provides an illustration of feature vector creation.
- FIGS. 5 ( a )- 5 ( d ) are flow charts illustrating several methods of performing entity type assignment.
- FIG. 1 shows a system architecture 100 adapted to support one embodiment.
- 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 a 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 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 the 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' birthday is “Dec. 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 Dec. 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, one source page for this fact will contain an exact match of the fact while another source page will contain text that is considered synonymous with the fact.
- the build engine 112 builds and manages the repository 115 .
- the service engine 114 is an interface for querying the repository 115 .
- the 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 the janitor 110 .
- the 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.
- the 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 the repository 115 are described below, in relation to FIGS. 2( a )- 2 ( d ).
- the importer 108 provides facts directly to the build engine 112 and/or repository 115 .
- the janitors 110 operate on the facts and/or objects in the repository 115 .
- the 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 the data processing system 106 instead of being coupled to the data processing system 106 by a network.
- importer the 108 may import facts from a database that is a part of or associated with the data processing system 106 .
- FIG. 1 also includes components to access the repository 115 on behalf of one or more object requesters 152 , 154 .
- Object requesters are entities that request objects from the 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 the data processing system 106 .
- the blog may include a reference to an object whose facts are in the 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 an object requester 154 , requesting the facts of objects from the repository 115 .
- FIG. 1 shows that the data processing system 106 includes a memory 107 and one or more processors 116 .
- the memory 107 includes the importers 108 , janitors 110 , build engine 112 , service engine 114 , and requester 154 , each of which is preferably implemented as instructions stored in memory 107 and executable by processor 116 .
- Memory 107 also includes the repository 115 .
- the 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 , the build engine 112 , the service engine 114 , the requester 154 , and at least some portions of the repository 115 .
- FIG. 1 also includes one or more input/output devices 120 that allow data to be input and output to and from the data processing system 106 . It will be understood that embodiments of the data processing system 106 also include standard software components such as operating systems and the like and further include 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 the repository 115 , according to some embodiments.
- 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 the 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, and 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 115 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 the repository 115 , according to some embodiments, 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 the 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 an object reference link 216 that contains the object ID for the “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 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 fields (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 fact 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 set 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 the repository 115 .
- FIG. 2( e ) is a block diagram illustrating an alternate data structure 290 for facts and objects in accordance with 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 .
- an object may explicitly exist in the repository 115 , or it may exist merely as a collection of facts with a common object ID.
- a fact is associated with an object by sharing a common object ID with other facts. For example, a fact could be associated with an object of a given type by sharing a common object ID at least with a type fact indicating the given type (or as another example, with a category fact indicating a particular category of object).
- facts and objects can be stored in a variety of structures, such as fact and/or object repositories.
- structures such as fact and/or object repositories.
- repository 115 it should be understood that various embodiments may store facts and/or objects in a variety of data structures.
- FIG. 3 is a block diagram illustrating an entity type assignment engine 300 according to one embodiment.
- the entity type assignment engine 300 improves the quality of knowledge contained within the repository 115 by assigning entity types to objects with unknown entity type.
- the entity type of an object is the category of the “real world thing” or entity the set of facts contained within the object describe.
- Example entity types include “Book”, “Movie”, “Country”, and “Person”.
- an entity type is represented as a special kind of fact associated with an object.
- an entity may have a single entity type or multiple entity types. Some pairs or sets of entity types may be specified as conflicting. For instance, an object cannot be both a “Book” and a “Person”. In some embodiments, non-conflicting entity types may be associated with an object. For instance, an object can have entity types for both a “Person” and a “Politician”.
- the entity type assignment engine 300 identifies objects in the repository 115 with unknown entity type and assigns entity types to these objects. Once assigned an entity type, objects are either stored in the repository 115 in place of, or in addition to the original objects with unknown entity type. Depending on the embodiment, additional information may be added to the repository 115 such as a new or updated metric 218 representing improved quality of the facts 204 . New or updated metrics 218 can include the confidence level and the importance level of the facts 104 .
- An embodiment of the entity type assignment engine 300 is implemented as a janitor 110 .
- the entity type assignment engine 300 can also be implemented by other entities shown in FIG. 1 and/or by another entity altogether.
- FIG. 3 illustrates that the entity type assignment engine 300 includes multiple modules for performing various functions. Some embodiments include different and/or additional modules than the ones shown in FIG. 3 .
- the functions attributed to the modules herein can be distributed among the modules in different ways.
- An entity type model module 301 identifies the objects in the repository 115 with known entity types and generates entity type models representing each entity type. According to the embodiment, the entity type model module 301 may generate entity type models once or continuously regenerate entity type models to incorporate new objects with known or assigned entity type. Entity type models can be rebuilt continuously or at set time intervals such as every hour, day or week. Additionally, entity type models may be rebuilt based on the addition of new objects with known or assigned entity type to the repository.
- a binary classifier is built for each entity type (e.g. “Dog”, “Book”, “Country”) providing an entity type model of each entity type relative to all other entity types.
- a binary classifier for entity type “Dog” would classify objects as either “Dogs” or “Non-Dogs”.
- Binary classifiers can be created with any type of binary classification algorithm such as support vector machines, neural networks, maximum entropy, boosting, bagging, and online gradient descent learning. Other binary classification algorithms will be apparent to those skilled in the art.
- a multi-class classifier is created by the entity type model module 301 created in place of, or in conjunction with, binary classifiers. As opposed to a binary classifier, a multi-class classifier creates a classification model or models for all entity types. Using the above example, a multi-class classifier creates models for and classifies an object as one of “Dog”, “Book” and “Country”. Though any multi-class classification algorithm may be employed in this method, some embodiments may include multi-class classification algorithms such as multi-class support vector machines, or maximum entropy.
- the entity type model module 301 uses generative techniques to create entity type models.
- Generative techniques can incorporate unsupervised or semi-supervised approaches to learn models of data.
- Unsupervised approaches such as clustering, expectation maximization or self-organizing maps automatically group data based on pattern recognition.
- Semi-supervised approaches such as n-means clustering, or transductive support vector machines contain some portion of data which is labeled according to entity type which directs pattern recognition. Other techniques for generative learning will be apparent to those skilled in the art.
- the groups of data created using generative techniques are combined by the entity type model module 301 to form entity type models.
- One method of combining data from generative models is to generate a prototype for each group or cluster which can be used as an entity type model.
- a prototype may be created by combining group data in any suitable way such as averaging data, weighting data, probabilistic methods or any combination thereof.
- the entity type assignment module 302 identifies objects of unknown entity type in the repository and assigns entity types to the objects of unknown entity type.
- the entity type assignment module 302 uses the classifiers and generative models computed by the entity type model module 301 to generate values used to assign entity type. According to the entity type model used, the values can represent a similarity to an entity type, the probability of an object having an entity type or a confidence value that the object has an entity type.
- the object of unknown entity type is assigned an entity type by the entity type assignment module 302 based on a single value generated based on a single entity type model such as a binary classifier. If the generated single value is greater or less than a specified cutoff value, the object of unknown entity type is assigned the entity type of the model.
- the entity type assignment module 302 compares the object of unknown entity type to multiple classification models representing multiple entity types and assigns entity type based on multiple values. In embodiments where multiple values are generated, the entity type with the highest or lowest value can be selected for assigning an entity to the object of unknown entity type. Again, a threshold or cutoff value can be applied to the highest or lowest value to increase the stringency.
- the entity type assignment module 302 will not assign objects of unknown entity an entity type due to weak probability or similarity values. Similarly, objects with same or close values for conflicting entity types will be identified as having conflicting values and will not be assigned an entity type.
- the object update module 304 uses information from the entity type assignment module 302 to update the objects in the repository 115 with assigned entity types. In embodiments where entity type is represented by a fact, a new fact specifying entity type is added to the object.
- the object update module 304 may perform additional actions to clean up the repository. According to the embodiment, the object update module 304 may perform these actions as part of the entity type assignment engine 300 or in communication with another janitor 110 .
- the object update module 304 can update other object information such as the metrics 218 associated with the facts 204 .
- the metrics 218 contain values representative of the confidence and importance of the fact. Newly assigned entity types can be used to reweigh other facts associated with the entities based on strong correlations between entity types and attributes 212 or values 214 . In embodiments where entity type is represented as a fact 204 , the confidence of the entity type fact can be increased due to entity type assignment.
- the object update module 304 identifies relationships between objects based on assigned entity type. Relationships can be represented as facts where the value 214 is another entity represented by another object, for instance, (spouse Hillary Clinton Bill Clinton). If we know that the value 214 described by the attribute 212 ‘spouse’ is supposed to be a Person, then an object for Bill Clinton with entity type Person can be associated with the value.
- the feature vector module 303 processes object data into feature vectors for use by the entity type assignment 302 and entity type model 301 modules.
- the feature vector module 303 creates several data points or features from the fact data associated with an object in the repository 115 .
- Features can be represented in any way, such as text strings or alphanumeric symbols.
- Features can incorporate any data contained in or associated with the fact or objects.
- Name facts 207 and property facts 209 are special types of facts which also may be incorporated into features.
- feature vectors will contain features derived from data contained in the attribute 212 fields of the facts. Attributes 212 are represented within a field or slot in a feature vector.
- Value 214 data in conjunction with attribute 212 data. Attribute 212 and value 214 data can be combined or concatenated into one representative feature. Numerical value 214 data may be binned or discretized in feature generation. Additionally, values may be incorporated which represent a closed set of categorical values such as genre or color.
- Attribute annotations may include various data associated with the attribute such as the entity type of the value they describe. For instance, the attribute “dateOfBirth” can have an annotation of “Date” representing the type of the value it describes. Attribute and annotation information can be combined in a single feature.
- features can also represent any information associated with the fact.
- An example of this is the source 220 of the fact such as the Uniform Resource Locator or the website from which the fact was collected or extracted.
- the feature vector can also contain a weight representing the significance of a feature.
- Features may be weighted according to the metrics 218 associated with facts from with they were derived. Similarly, features may be weighted by the source 220 or importer 108 used to generate the fact. Features may also be weighted according to the type of fact from which they were derived. Different types of facts may be assigned different weights. For instance, special types of facts such as entity type facts or name facts 207 may be given a higher weight.
- FIG. 4 is a diagram illustrating feature vector creation according to one embodiment.
- three objects 402 are translated into feature vectors 404 .
- the facts 403 are translated into features 405 based on an attribute contained within a fact or the attribute and the value of the fact. Additionally, the source of the information is translated into a feature value.
- features 405 contain symbols ‘a’, ‘av’, and ‘s’ respectively used to denote that the feature contains an attribute 212 , an attribute value 214 , and the sources 220 of the facts 403 contained in the objects.
- the symbols are separated from the attribute with colons.
- the values are further separated from the attributes by colons.
- the embodiment illustrated provides an example of value discretization or “binning”.
- the translation of the values 214 for attribute 212 ‘height’ from facts into features transforms the fact values into an order to magnitude in meters. For instance, as George Bush is over 1 meter, the feature describing his height in magnitude of meters has a value of 0. Likewise, as the book Grapes of Wrath is less than 1 meter, the feature describing the height of the book in magnitude of meters has a value of ⁇ 1.
- FIGS. 5( a )- 5 ( d ) are flow charts illustrating steps performed by the entity type assignment engine 300 to assign entity types to objects in the repository 115 according to various embodiments of the present invention. Other embodiments perform different and/or additional steps than the ones shown in the figures described below. In addition, other embodiments perform the steps in different orders.
- FIG. 5( a ) is a flow chart illustrating the high level steps of assigning entity types according to an embodiment. Initially, the entity type model module 301 and the entity type assignment module 302 respectively identify 510 the objects in the repository with known and unknown entity types.
- the feature vector module 303 generates 512 feature vectors for all the objects in the repository 115 .
- the feature vector module identifies 512 facts associated with the objects and generates 512 features based on these facts. As discussed above, the feature vector module 303 generates 512 features that contain the attribute and value of the facts.
- the feature vector module 303 also generates 512 features that contain information associated with the facts such as annotations or the source of the facts.
- the entity type model module 301 generates 514 entity type models based on the entity type of the model. Embodiments that use binary classifiers, multi-class classifiers and generative techniques to generate 514 entity type models are illustrated in FIGS. 5 b - 5 d and are discussed in detail below.
- the entity type assignment module 302 applies 516 the set of entity type models generated by the entity type model module 301 to the objects of unknown entity type in order to generate 516 values which indicate the probability that the object of unknown entity type is of an entity type.
- the entity type assignment module 302 selects the highest value of the generated values for entity type assignment 516 .
- the entity type assignment module also compares 516 the values with known conflicting entity types. If the object of unknown entity has similar values for two conflicting types, the object will not be assigned 516 a value. Otherwise, if the highest value generated is above a certain threshold, the object will be assigned 516 the entity type of the model used to generate that value.
- the object update module 304 stores 518 the objects with assigned entity type in the repository 115 .
- the object update module creates 518 a new fact specifying entity type which is associated with the objects of unknown entity to which entity type was assigned in step 512 .
- the process of assigning entity types may be iterated 519 to include the objects with assigned entity type in the entity type models.
- binary classification models are generated 524 for each entity type.
- a binary classifier is built 524 by the entity type model module 301 .
- the binary classifier is a stochastic gradient descent learning algorithm and a binary classifier is built 524 for each entity type contained within the objects of known entity type.
- objects are separated 524 into two classes, objects of a specific entity type and the set of all objects that are not of the specific entity type.
- stochastic gradient descent learning the features associated with the objects of the two classes are plotted in space. This plot is used to learn a geometric function which separates the two classes based on the features. This geometric function is used by the entity type assignment module 302 to assign entity types to objects of unknown entity type.
- the entity type assignment module 302 applies 526 the function learned by the gradient descent algorithm for each entity type to each of the objects of unknown entity type.
- the entity type assignment module calculates a set of probability values for each object indicative of the probability the object is of each entity type (e.g. Dog 10%, Person 50%, Book 85%, Movie 92%).
- FIG. 5( c ) is a flow chart illustrating an embodiment using multi-class classifiers.
- a multi-class classifier is built 534 by the entity type model module 301 .
- the multi-class classifier is built using a maximum entropy algorithm.
- the maximum entropy algorithm learns an entity type model represented by a set of “constraints” or expected values for the features associated with each entity type that characterize the distribution of features for the entity type.
- These learned models are then applied 536 by the entity type assignment module 302 as a multi-class classifier to estimate the conditional distribution of an object with unknown entity type. From the conditional distribution, a value indicative of the probability the object of unknown entity type has the entity type of the learned model is generated.
- FIG. 5( d ) is a flow chart illustrating the use of generative models such as mixture models to create entity type models according to one embodiment.
- Objects with known entity type are used learn groups or clusters of data representing entity types.
- the entity type model module 301 identifies all objects with known entity type and clusters them using, for example, simple bucketing. These techniques create a fixed number of clusters representing the number of different entity types.
- the resultant clusters are given a semantic label representing the entity type of the cluster 542 .
- Clusters with semantic labels are used to generate 544 entity type cluster prototypes.
- the entity type cluster prototypes are represented as vectors of probabilities, each probability associated with a feature. Each probability is determined by looking up the number of objects that have the feature and determining the fraction of occurrences of the feature over the different entity types associated with the objects. For example, the attribute ‘mother’ is identified as occurring 30 times in objects with entity type “Person”, 14 times in objects with entity type “Dog” and 1 time in an object with entity type “Country”. These numbers are then normalized to sum up to one. Using the above example would provide the following values: 0.66 for Person, 0.31 for Dog and 0.03 for Country. These normalized numbers are then associated with the features in the entity type cluster prototypes to represent the probability of the feature given the entity type of the entity type cluster prototype.
- the entity type cluster prototypes are used by the entity type assignment module 302 to calculate 546 similarity values for objects of unknown entity type.
- the feature vectors created for the objects of unknown entity type are compared to the entity type cluster prototypes to calculate a similarity metric for each cluster prototype.
- the value of each feature associated with an object of unknown entity is identified as a probability in the cluster prototype.
- the identified probability values are then summed or combined to create a similarity value or “distance” between the object of unknown entity type and the entity type cluster prototypes.
- the similarity values are used to assign entity type to objects of unknown entity type based on the nearest cluster prototype as defined by the similarity values or “distances”.
- Semi-supervised learning approaches use both labeled and unlabelled data to learn statistical models for classification.
- the objects of unknown entity type may be used to refine 545 the cluster prototypes using semi-supervised learning such as expectation maximization.
- Expectation maximization is a two step learning algorithm, which is repeated until convergence.
- the feature vectors for each object are compared to the cluster prototypes using a set distance metric.
- the distances between the object of unknown entity type (e.g. object X) and the cluster prototypes are then normalized 545 to 1 representing the posterior probabilities that object X has each entity type.
- Object X is now fractionally assigned to several different clusters. Consequently, the features contained within object X now fractionally occur in the different entity type cluster prototypes.
- the entity type cluster prototypes are re-generated as in step 544 incorporating the posterior probabilities.
- the fractional assignment of objects to entity type clusters is used to weight the features in the entity type cluster prototype generation.
- the expectation and maximization steps are iterated 545 until the cluster prototypes are stable, that is the probabilities associated with the features do not change over iterations between the two steps and the posterior probabilities associated with the objects of unknown entity type do not change.
- the refined entity type cluster prototypes are used by the entity type assignment module 302 to calculate 546 similarity values for objects of unknown entity type.
- entity types are assigned to objects with unknown entity type.
- entity types are assigned to objects with unknown entity type.
- Various embodiments of generating entity type models, generating feature vectors and assigning entity types are disclosed herein. The process of assigning entity type to objects with unknown entity type may be performed iteratively.
- 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 can be embodied in software, firmware or hardware, and when embodied in software, can be downloaded to reside on and be operated from different platforms used by a variety of 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 in 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.
Abstract
A computer system creates a plurality of objects using facts derived from electronic documents, each object including one or more facts describing an entity associated with the object. The system generates a value for an object of an unknown entity type, of the plurality of objects, by using an entity type model for a known entity type. The entity type model is based on a set of features of a plurality of objects of the known entity type, and the value indicates whether the object of an unknown entity type is of the known entity type. The system assigns the known entity type to the object of an unknown entity type in response to a determination that the value indicates the object of an unknown entity type is of the known entity type, and stores the object with the assigned entity type.
Description
- This application is a continuation of U.S. patent application Ser. No. 11/781,891, filed Jul. 23, 2007, entitled “Entity Type Assignment”, which is incorporate by reference herein in its entirety.
- The disclosed embodiments generally relate to fact databases or repositories. Specifically, the disclosed embodiments relate to methods of learning entity type models from objects in fact repositories and using these models to assign entity types to objects of unknown entity type in the fact repository.
- Computational techniques such as information extraction are used to automatically identify and extract information in the form of facts. Information extraction can be performed on a variety of sources such as web pages to extract fact data. A set of facts collected from a source describing the same entity may be organized and can be stored as an object in a repository of facts.
- Facts contain an attribute that describes an entity. The entity type of the entity is the type of real world thing the object represents (e.g. Person, Dog, Book, Movie). Entity type can be defined in a fact associated with the object. This entity type information is necessary to understand relationships between sets of facts associated with different objects. For example, an object with entity name “Hillary Clinton” is associated with a fact, “spouse Bill Clinton” and it is known that the attribute “spouse” always has a value with entity type “Person”. Knowing that an object with entity name “Bill Clinton” has an entity type of “Person” enables the identification of a relationship between the two objects.
- These relationships can be used to organize the sets of facts. Similarly, in cases where it is unclear whether or not a fact is valid, entity type is used in association with the attribute defined by the fact to assign a confidence to the fact. For example, an object with entity name “Bill Clinton” has an attribute “genre” with an associated value “political”. If we know “genre” is only is used to describe a closed set of entity types such as “Book” and “Movie”, knowing that “Bill Clinton” is of entity type “Book” can provide a better confidence in that fact.
- Often the entity type of the entity represented by the object is unknown or confounded for a number of reasons. For instance, entity type information may not be available in the source data. Due to inherent error in information extraction, entity type information may not be extracted. The entity type of an object may also be confounded by several objects having the same name. For example, an object with entity name “Bill Clinton” could be either an object with entity type “Person” or an object with entity type “Book”.
- What is needed then is a computational method of assigning entity types to objects.
- The above and other needs are met by methods, systems, and computer program products that assign entity types to objects with unknown entity type. Embodiments of the method comprise identifying a plurality of objects derived from electronic documents, each object including one or more facts describing an entity with which the object is associated, wherein each fact comprises an attribute. The method generates a set of features describing the facts included with the object for each of the plurality of objects. The method further identifies a subset of the plurality of objects of a known entity type. The method further generates an entity type model based on the sets of features generated for the objects in the identified subset. The method also generates a value based on an object of unknown entity type and the entity type model, wherein the value indicates whether the object of unknown entity type is of the known entity type. The method assigns the known entity type to the object of unknown entity type responsive to a determination that the value indicates the object of unknown entity type is of the known entity type and stores the object to which the known entity type was assigned.
- Embodiments of the system and computer program product comprise a repository which stores a plurality of objects derived from electronic documents, each object including one or more facts describing an entity with which the object is associated, wherein each fact comprises an attribute. The system and computer program product also comprise a feature generation module adapted to generate, for each of the plurality of objects, a set of features describing the facts included with the object. An entity type model module adapted to generate an entity type model based on the sets of features generated for a subset of objects of a known entity type. The system and computer product further comprise an entity type model module adapted to generate an entity type model based on the sets of features generated for a subset of objects of a known entity type. The system and computer product further comprise an entity type assignment module adapted to generate a value based on an object of unknown entity type and the entity type model, wherein the value indicates whether the object of unknown entity type is of the known entity type. Finally, an object update module stores the object to which the known entity type was assigned.
-
FIG. 1 shows a system architecture adapted to support one embodiment. -
FIGS. 2 (a)-2(d) are block diagrams illustrating a data structure for facts within a repository ofFIG. 1 in accordance with some embodiments. -
FIG. 2( e) is a block diagram illustrating an alternate data structure for facts and objects in accordance with some embodiments. -
FIG. 3 . is a block diagram illustrating an entity type assignment engine according to one embodiment. -
FIG. 4 provides an illustration of feature vector creation. -
FIGS. 5 (a)-5(d) are flow charts illustrating several methods of performing entity type assignment. - The figures depict various embodiments 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.
- Embodiments are now described with reference to the figures where like reference numbers indicate identical or functionally similar elements.
-
FIG. 1 shows asystem architecture 100 adapted to support one embodiment.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 a 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 therepository 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 by theimporter 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 from therepository 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' birthday is “Dec. 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 Dec. 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, one source page for this fact will contain an exact match of the fact while another source page will contain text that is considered synonymous with the fact. - The
build engine 112 builds and manages therepository 115. Theservice engine 114 is an interface for querying therepository 115. Theservice engine 114's main function is to process queries, score matching objects, and return them to the caller but it is also used by thejanitor 110. - The
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. - The
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 in therepository 115 are described below, in relation toFIGS. 2( a)-2(d). - Some embodiments operate on the facts and/or objects in different orders than described above. For example, in one embodiment the
importer 108 provides facts directly to thebuild engine 112 and/orrepository 115. Thejanitors 110, in turn, operate on the facts and/or objects in therepository 115. It should also be appreciated that in practice at least some of the components of thedata processing system 106 will be distributed over multiple computers, communicating over a network. For example, therepository 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 the
data processing system 106 instead of being coupled to thedata processing system 106 by a network. For example, importer the 108 may import facts from a database that is a part of or associated with thedata processing system 106. -
FIG. 1 also includes components to access therepository 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 in thedata processing system 106. For example, in a computer system hosting a blog, the blog may include a reference to an object whose facts are in therepository 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 anobject requester 154, requesting the facts of objects from therepository 115. -
FIG. 1 shows that thedata processing system 106 includes amemory 107 and one ormore processors 116. Thememory 107 includes theimporters 108,janitors 110, buildengine 112,service engine 114, andrequester 154, each of which is preferably implemented as instructions stored inmemory 107 and executable byprocessor 116.Memory 107 also includes therepository 115. Therepository 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, thebuild engine 112, theservice engine 114, therequester 154, and at least some portions of therepository 115.FIG. 1 also includes one or more input/output devices 120 that allow data to be input and output to and from thedata processing system 106. It will be understood that embodiments of thedata processing system 106 also include standard software components such as operating systems and the like and further include 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 therepository 115, according to some embodiments. 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 in therepository 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, and 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 therepository 115 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 within therepository 115, according to some embodiments, 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 in therepository 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 anobject reference link 216 that contains the object ID for the “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 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 fields (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 fact 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 set 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 from therepository 115. -
FIG. 2( e) is a block diagram illustrating analternate data structure 290 for facts and objects in accordance with embodiments of the invention. In this data structure, anobject 290 contains an object 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. - As described above, an object may explicitly exist in the
repository 115, or it may exist merely as a collection of facts with a common object ID. Reference is made to particular objects for the purposes of illustration; one of skill in the art will recognized that the systems and methods described herein are applicable to a variety of implementations and that such references are not limiting. When reference is made to a fact being associated with an object, it should be understood that in at least one embodiment a fact is associated with an object by sharing a common object ID with other facts. For example, a fact could be associated with an object of a given type by sharing a common object ID at least with a type fact indicating the given type (or as another example, with a category fact indicating a particular category of object). Furthermore, in various embodiments, facts and objects can be stored in a variety of structures, such as fact and/or object repositories. When reference is made herein to therepository 115, it should be understood that various embodiments may store facts and/or objects in a variety of data structures. -
FIG. 3 . is a block diagram illustrating an entitytype assignment engine 300 according to one embodiment. The entitytype assignment engine 300 improves the quality of knowledge contained within therepository 115 by assigning entity types to objects with unknown entity type. The entity type of an object is the category of the “real world thing” or entity the set of facts contained within the object describe. Example entity types include “Book”, “Movie”, “Country”, and “Person”. In some embodiments, an entity type is represented as a special kind of fact associated with an object. - According to the embodiment, an entity may have a single entity type or multiple entity types. Some pairs or sets of entity types may be specified as conflicting. For instance, an object cannot be both a “Book” and a “Person”. In some embodiments, non-conflicting entity types may be associated with an object. For instance, an object can have entity types for both a “Person” and a “Politician”.
- The entity
type assignment engine 300 identifies objects in therepository 115 with unknown entity type and assigns entity types to these objects. Once assigned an entity type, objects are either stored in therepository 115 in place of, or in addition to the original objects with unknown entity type. Depending on the embodiment, additional information may be added to therepository 115 such as a new or updated metric 218 representing improved quality of thefacts 204. New or updatedmetrics 218 can include the confidence level and the importance level of thefacts 104. - An embodiment of the entity
type assignment engine 300 is implemented as ajanitor 110. However, the entitytype assignment engine 300 can also be implemented by other entities shown inFIG. 1 and/or by another entity altogether.FIG. 3 illustrates that the entitytype assignment engine 300 includes multiple modules for performing various functions. Some embodiments include different and/or additional modules than the ones shown inFIG. 3 . Moreover, the functions attributed to the modules herein can be distributed among the modules in different ways. - An entity
type model module 301 identifies the objects in therepository 115 with known entity types and generates entity type models representing each entity type. According to the embodiment, the entitytype model module 301 may generate entity type models once or continuously regenerate entity type models to incorporate new objects with known or assigned entity type. Entity type models can be rebuilt continuously or at set time intervals such as every hour, day or week. Additionally, entity type models may be rebuilt based on the addition of new objects with known or assigned entity type to the repository. - Depending on the particular embodiment, different kinds of entity type models may be built by the entity
type model module 301. In one embodiment, a binary classifier is built for each entity type (e.g. “Dog”, “Book”, “Country”) providing an entity type model of each entity type relative to all other entity types. For example, a binary classifier for entity type “Dog” would classify objects as either “Dogs” or “Non-Dogs”. Binary classifiers can be created with any type of binary classification algorithm such as support vector machines, neural networks, maximum entropy, boosting, bagging, and online gradient descent learning. Other binary classification algorithms will be apparent to those skilled in the art. - In some embodiments, a multi-class classifier is created by the entity
type model module 301 created in place of, or in conjunction with, binary classifiers. As opposed to a binary classifier, a multi-class classifier creates a classification model or models for all entity types. Using the above example, a multi-class classifier creates models for and classifies an object as one of “Dog”, “Book” and “Country”. Though any multi-class classification algorithm may be employed in this method, some embodiments may include multi-class classification algorithms such as multi-class support vector machines, or maximum entropy. - In some embodiments, the entity
type model module 301 uses generative techniques to create entity type models. Generative techniques can incorporate unsupervised or semi-supervised approaches to learn models of data. Unsupervised approaches such as clustering, expectation maximization or self-organizing maps automatically group data based on pattern recognition. Semi-supervised approaches such as n-means clustering, or transductive support vector machines contain some portion of data which is labeled according to entity type which directs pattern recognition. Other techniques for generative learning will be apparent to those skilled in the art. - The groups of data created using generative techniques are combined by the entity
type model module 301 to form entity type models. One method of combining data from generative models is to generate a prototype for each group or cluster which can be used as an entity type model. A prototype may be created by combining group data in any suitable way such as averaging data, weighting data, probabilistic methods or any combination thereof. - The entity
type assignment module 302 identifies objects of unknown entity type in the repository and assigns entity types to the objects of unknown entity type. The entitytype assignment module 302 uses the classifiers and generative models computed by the entitytype model module 301 to generate values used to assign entity type. According to the entity type model used, the values can represent a similarity to an entity type, the probability of an object having an entity type or a confidence value that the object has an entity type. - According to the embodiment, the object of unknown entity type is assigned an entity type by the entity
type assignment module 302 based on a single value generated based on a single entity type model such as a binary classifier. If the generated single value is greater or less than a specified cutoff value, the object of unknown entity type is assigned the entity type of the model. - In some embodiments, the entity
type assignment module 302 compares the object of unknown entity type to multiple classification models representing multiple entity types and assigns entity type based on multiple values. In embodiments where multiple values are generated, the entity type with the highest or lowest value can be selected for assigning an entity to the object of unknown entity type. Again, a threshold or cutoff value can be applied to the highest or lowest value to increase the stringency. - Using cutoff values, the entity
type assignment module 302 will not assign objects of unknown entity an entity type due to weak probability or similarity values. Similarly, objects with same or close values for conflicting entity types will be identified as having conflicting values and will not be assigned an entity type. - The
object update module 304 uses information from the entitytype assignment module 302 to update the objects in therepository 115 with assigned entity types. In embodiments where entity type is represented by a fact, a new fact specifying entity type is added to the object. Theobject update module 304 may perform additional actions to clean up the repository. According to the embodiment, theobject update module 304 may perform these actions as part of the entitytype assignment engine 300 or in communication with anotherjanitor 110. - In addition to updating entity types, the
object update module 304 can update other object information such as themetrics 218 associated with thefacts 204. Themetrics 218 contain values representative of the confidence and importance of the fact. Newly assigned entity types can be used to reweigh other facts associated with the entities based on strong correlations between entity types and attributes 212 or values 214. In embodiments where entity type is represented as afact 204, the confidence of the entity type fact can be increased due to entity type assignment. - In some embodiments, the
object update module 304 identifies relationships between objects based on assigned entity type. Relationships can be represented as facts where thevalue 214 is another entity represented by another object, for instance, (spouse Hillary Clinton Bill Clinton). If we know that thevalue 214 described by the attribute 212 ‘spouse’ is supposed to be a Person, then an object for Bill Clinton with entity type Person can be associated with the value. - The
feature vector module 303 processes object data into feature vectors for use by theentity type assignment 302 andentity type model 301 modules. Thefeature vector module 303 creates several data points or features from the fact data associated with an object in therepository 115. Features can be represented in any way, such as text strings or alphanumeric symbols. - Features can incorporate any data contained in or associated with the fact or objects. Name
facts 207 andproperty facts 209 are special types of facts which also may be incorporated into features. In most embodiments, feature vectors will contain features derived from data contained in theattribute 212 fields of the facts.Attributes 212 are represented within a field or slot in a feature vector. - Features can also incorporate
value 214 data in conjunction withattribute 212 data.Attribute 212 andvalue 214 data can be combined or concatenated into one representative feature.Numerical value 214 data may be binned or discretized in feature generation. Additionally, values may be incorporated which represent a closed set of categorical values such as genre or color. - Additional annotation information can be associated with the
attribute 212. Attribute annotations may include various data associated with the attribute such as the entity type of the value they describe. For instance, the attribute “dateOfBirth” can have an annotation of “Date” representing the type of the value it describes. Attribute and annotation information can be combined in a single feature. - In additional to information contained within facts, features can also represent any information associated with the fact. An example of this is the
source 220 of the fact such as the Uniform Resource Locator or the website from which the fact was collected or extracted. - The feature vector can also contain a weight representing the significance of a feature. Features may be weighted according to the
metrics 218 associated with facts from with they were derived. Similarly, features may be weighted by thesource 220 orimporter 108 used to generate the fact. Features may also be weighted according to the type of fact from which they were derived. Different types of facts may be assigned different weights. For instance, special types of facts such as entity type facts orname facts 207 may be given a higher weight. -
FIG. 4 . is a diagram illustrating feature vector creation according to one embodiment. In the embodiment illustrated, threeobjects 402 are translated intofeature vectors 404. In the diagram, thefacts 403 are translated intofeatures 405 based on an attribute contained within a fact or the attribute and the value of the fact. Additionally, the source of the information is translated into a feature value. - In this embodiment, features 405 contain symbols ‘a’, ‘av’, and ‘s’ respectively used to denote that the feature contains an
attribute 212, anattribute value 214, and thesources 220 of thefacts 403 contained in the objects. The symbols are separated from the attribute with colons. In features containing values in addition to attributes, the values are further separated from the attributes by colons. - The embodiment illustrated provides an example of value discretization or “binning”. The translation of the
values 214 for attribute 212 ‘height’ from facts into features transforms the fact values into an order to magnitude in meters. For instance, as George Bush is over 1 meter, the feature describing his height in magnitude of meters has a value of 0. Likewise, as the book Grapes of Wrath is less than 1 meter, the feature describing the height of the book in magnitude of meters has a value of −1. -
FIGS. 5( a)-5(d) are flow charts illustrating steps performed by the entitytype assignment engine 300 to assign entity types to objects in therepository 115 according to various embodiments of the present invention. Other embodiments perform different and/or additional steps than the ones shown in the figures described below. In addition, other embodiments perform the steps in different orders. -
FIG. 5( a) is a flow chart illustrating the high level steps of assigning entity types according to an embodiment. Initially, the entitytype model module 301 and the entitytype assignment module 302 respectively identify 510 the objects in the repository with known and unknown entity types. - The
feature vector module 303 generates 512 feature vectors for all the objects in therepository 115. The feature vector module identifies 512 facts associated with the objects and generates 512 features based on these facts. As discussed above, thefeature vector module 303 generates 512 features that contain the attribute and value of the facts. Thefeature vector module 303 also generates 512 features that contain information associated with the facts such as annotations or the source of the facts. - The entity
type model module 301 generates 514 entity type models based on the entity type of the model. Embodiments that use binary classifiers, multi-class classifiers and generative techniques to generate 514 entity type models are illustrated inFIGS. 5 b-5 d and are discussed in detail below. - The entity
type assignment module 302 applies 516 the set of entity type models generated by the entitytype model module 301 to the objects of unknown entity type in order to generate 516 values which indicate the probability that the object of unknown entity type is of an entity type. The entitytype assignment module 302 selects the highest value of the generated values forentity type assignment 516. The entity type assignment module also compares 516 the values with known conflicting entity types. If the object of unknown entity has similar values for two conflicting types, the object will not be assigned 516 a value. Otherwise, if the highest value generated is above a certain threshold, the object will be assigned 516 the entity type of the model used to generate that value. - The
object update module 304stores 518 the objects with assigned entity type in therepository 115. The object update module creates 518 a new fact specifying entity type which is associated with the objects of unknown entity to which entity type was assigned instep 512. - The process of assigning entity types may be iterated 519 to include the objects with assigned entity type in the entity type models.
- In the embodiment illustrated in
FIG. 5( b), binary classification models are generated 524 for each entity type. Using the objects of known entity type, a binary classifier is built 524 by the entitytype model module 301. In a specific embodiment, the binary classifier is a stochastic gradient descent learning algorithm and a binary classifier is built 524 for each entity type contained within the objects of known entity type. In binary classification, objects are separated 524 into two classes, objects of a specific entity type and the set of all objects that are not of the specific entity type. In stochastic gradient descent learning, the features associated with the objects of the two classes are plotted in space. This plot is used to learn a geometric function which separates the two classes based on the features. This geometric function is used by the entitytype assignment module 302 to assign entity types to objects of unknown entity type. - The entity
type assignment module 302 applies 526 the function learned by the gradient descent algorithm for each entity type to each of the objects of unknown entity type. The entity type assignment module calculates a set of probability values for each object indicative of the probability the object is of each entity type (e.g. Dog 10%, Person 50%, Book 85%, Movie 92%). -
FIG. 5( c) is a flow chart illustrating an embodiment using multi-class classifiers. Using the objects of known entity type, a multi-class classifier is built 534 by the entitytype model module 301. In a specific embodiment, the multi-class classifier is built using a maximum entropy algorithm. Using the set of features associated with objects of different entity type, the maximum entropy algorithm learns an entity type model represented by a set of “constraints” or expected values for the features associated with each entity type that characterize the distribution of features for the entity type. - These learned models are then applied 536 by the entity
type assignment module 302 as a multi-class classifier to estimate the conditional distribution of an object with unknown entity type. From the conditional distribution, a value indicative of the probability the object of unknown entity type has the entity type of the learned model is generated. -
FIG. 5( d) is a flow chart illustrating the use of generative models such as mixture models to create entity type models according to one embodiment. Objects with known entity type are used learn groups or clusters of data representing entity types. The entitytype model module 301 identifies all objects with known entity type and clusters them using, for example, simple bucketing. These techniques create a fixed number of clusters representing the number of different entity types. The resultant clusters are given a semantic label representing the entity type of thecluster 542. - Clusters with semantic labels are used to generate 544 entity type cluster prototypes. The entity type cluster prototypes are represented as vectors of probabilities, each probability associated with a feature. Each probability is determined by looking up the number of objects that have the feature and determining the fraction of occurrences of the feature over the different entity types associated with the objects. For example, the attribute ‘mother’ is identified as occurring 30 times in objects with entity type “Person”, 14 times in objects with entity type “Dog” and 1 time in an object with entity type “Country”. These numbers are then normalized to sum up to one. Using the above example would provide the following values: 0.66 for Person, 0.31 for Dog and 0.03 for Country. These normalized numbers are then associated with the features in the entity type cluster prototypes to represent the probability of the feature given the entity type of the entity type cluster prototype.
- The entity type cluster prototypes are used by the entity
type assignment module 302 to calculate 546 similarity values for objects of unknown entity type. The feature vectors created for the objects of unknown entity type are compared to the entity type cluster prototypes to calculate a similarity metric for each cluster prototype. The value of each feature associated with an object of unknown entity is identified as a probability in the cluster prototype. The identified probability values are then summed or combined to create a similarity value or “distance” between the object of unknown entity type and the entity type cluster prototypes. The similarity values are used to assign entity type to objects of unknown entity type based on the nearest cluster prototype as defined by the similarity values or “distances”. - Semi-supervised learning approaches use both labeled and unlabelled data to learn statistical models for classification. According to the embodiment, the objects of unknown entity type may be used to refine 545 the cluster prototypes using semi-supervised learning such as expectation maximization. Expectation maximization is a two step learning algorithm, which is repeated until convergence.
- In the expectation step, the feature vectors for each object are compared to the cluster prototypes using a set distance metric. The distances between the object of unknown entity type (e.g. object X) and the cluster prototypes are then normalized 545 to 1 representing the posterior probabilities that object X has each entity type. Object X is now fractionally assigned to several different clusters. Consequently, the features contained within object X now fractionally occur in the different entity type cluster prototypes.
- In the maximization step, the entity type cluster prototypes are re-generated as in
step 544 incorporating the posterior probabilities. The fractional assignment of objects to entity type clusters is used to weight the features in the entity type cluster prototype generation. - The expectation and maximization steps are iterated 545 until the cluster prototypes are stable, that is the probabilities associated with the features do not change over iterations between the two steps and the posterior probabilities associated with the objects of unknown entity type do not change. The refined entity type cluster prototypes are used by the entity
type assignment module 302 to calculate 546 similarity values for objects of unknown entity type. - Through the construction of entity type models based on generated feature vectors, entity types are assigned to objects with unknown entity type. Various embodiments of generating entity type models, generating feature vectors and assigning entity types are disclosed herein. The process of assigning entity type to objects with unknown entity type may be performed iteratively.
- Reference in the specification to “one embodiment” or to “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiments are included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment.
- Some portions of the above are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. 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. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps (instructions) leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic or optical signals capable of being stored, transferred, combined, compared and otherwise manipulated. It is convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. Furthermore, it is also convenient at times, to refer to certain arrangements of steps requiring physical manipulations of physical quantities as modules or code devices, without loss of generality.
- It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or “determining” 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 can be embodied in software, firmware or hardware, and when embodied in software, can be downloaded to reside on and be operated from different platforms used by a variety of 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 in 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 displays 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 appear from the description below. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any references below to specific languages are provided for disclosure of enablement and best mode of the present invention.
- While the invention has been particularly shown and described with reference to a preferred embodiment and several alternate embodiments, it will be understood by persons skilled in the relevant art that various changes in form and details can be made therein without departing from the spirit and scope of the invention.
- 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 computer-implemented method of assigning an entity type to an object of an unknown entity type at a computer system, the computer system comprising one or more processors and memory storing one or more programs, the object stored in the memory, the method comprising:
creating a plurality of objects using facts derived from electronic documents, each object including one or more facts describing an entity with which the object is associated, wherein each fact comprises an attribute;
generating a value for an object of an unknown entity type, of the plurality of objects, by using an entity type model for a known entity type, wherein the entity type model is based on a set of features of a plurality of objects of the known entity type, and the value indicates whether the object of unknown entity type is of the known entity type;
assigning the known entity type to the object of unknown entity type in response to a determination that the value indicates the object of unknown entity type is of the known entity type; and
storing the object to which the known entity type was assigned with the assigned entity type.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/171,296 US20120136859A1 (en) | 2007-07-23 | 2011-06-28 | Entity Type Assignment |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/781,891 US7970766B1 (en) | 2007-07-23 | 2007-07-23 | Entity type assignment |
US13/171,296 US20120136859A1 (en) | 2007-07-23 | 2011-06-28 | Entity Type Assignment |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/781,891 Continuation US7970766B1 (en) | 2007-07-23 | 2007-07-23 | Entity type assignment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120136859A1 true US20120136859A1 (en) | 2012-05-31 |
Family
ID=44169488
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/781,891 Active 2028-07-24 US7970766B1 (en) | 2007-07-23 | 2007-07-23 | Entity type assignment |
US13/171,296 Abandoned US20120136859A1 (en) | 2007-07-23 | 2011-06-28 | Entity Type Assignment |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/781,891 Active 2028-07-24 US7970766B1 (en) | 2007-07-23 | 2007-07-23 | Entity type assignment |
Country Status (1)
Country | Link |
---|---|
US (2) | US7970766B1 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160092475A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Automated entity correlation and classification across heterogeneous datasets |
US20180173694A1 (en) * | 2016-12-21 | 2018-06-21 | Industrial Technology Research Institute | Methods and computer systems for named entity verification, named entity verification model training, and phrase expansion |
US10210246B2 (en) | 2014-09-26 | 2019-02-19 | Oracle International Corporation | Techniques for similarity analysis and data enrichment using knowledge sources |
US10885056B2 (en) | 2017-09-29 | 2021-01-05 | Oracle International Corporation | Data standardization techniques |
US10891272B2 (en) | 2014-09-26 | 2021-01-12 | Oracle International Corporation | Declarative language and visualization system for recommended data transformations and repairs |
US10936599B2 (en) | 2017-09-29 | 2021-03-02 | Oracle International Corporation | Adaptive recommendations |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI337712B (en) * | 2006-10-30 | 2011-02-21 | Inst Information Industry | Systems and methods for measuring behavior characteristics, and machine readable medium thereof |
US8666730B2 (en) * | 2009-03-13 | 2014-03-04 | Invention Machine Corporation | Question-answering system and method based on semantic labeling of text documents and user questions |
US8560468B1 (en) * | 2011-02-10 | 2013-10-15 | Google Inc. | Learning expected values for facts |
US9552352B2 (en) | 2011-11-10 | 2017-01-24 | Microsoft Technology Licensing, Llc | Enrichment of named entities in documents via contextual attribute ranking |
CN104428767B (en) | 2012-02-22 | 2018-02-06 | 谷歌公司 | For identifying the mthods, systems and devices of related entities |
US9424353B2 (en) * | 2012-02-22 | 2016-08-23 | Google Inc. | Related entities |
US20140052647A1 (en) * | 2012-08-17 | 2014-02-20 | Truth Seal Corporation | System and Method for Promoting Truth in Public Discourse |
US20140136494A1 (en) * | 2012-11-14 | 2014-05-15 | Homer Tlc, Inc. | System and method for automatic wrapper induction by applying filters |
US9292797B2 (en) * | 2012-12-14 | 2016-03-22 | International Business Machines Corporation | Semi-supervised data integration model for named entity classification |
US9264387B2 (en) | 2013-02-06 | 2016-02-16 | Msc Intellectual Properties B.V. | System and method for authorship disambiguation and alias resolution in electronic data |
US10380486B2 (en) * | 2015-01-20 | 2019-08-13 | International Business Machines Corporation | Classifying entities by behavior |
US10198491B1 (en) | 2015-07-06 | 2019-02-05 | Google Llc | Computerized systems and methods for extracting and storing information regarding entities |
US10102291B1 (en) | 2015-07-06 | 2018-10-16 | Google Llc | Computerized systems and methods for building knowledge bases using context clouds |
CN107885719B (en) * | 2017-09-20 | 2021-06-11 | 北京百度网讯科技有限公司 | Vocabulary category mining method and device based on artificial intelligence and storage medium |
US11544586B2 (en) * | 2018-11-29 | 2023-01-03 | Paypal, Inc. | Detecting incorrect field values of user submissions using machine learning techniques |
US11556845B2 (en) * | 2019-08-29 | 2023-01-17 | International Business Machines Corporation | System for identifying duplicate parties using entity resolution |
US11544477B2 (en) | 2019-08-29 | 2023-01-03 | International Business Machines Corporation | System for identifying duplicate parties using entity resolution |
US20220358151A1 (en) * | 2021-05-10 | 2022-11-10 | Microsoft Technology Licensing, Llc | Resource-Efficient Identification of Relevant Topics based on Aggregated Named-Entity Recognition Information |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040167907A1 (en) * | 2002-12-06 | 2004-08-26 | Attensity Corporation | Visualization of integrated structured data and extracted relational facts from free text |
US20050055365A1 (en) * | 2003-09-09 | 2005-03-10 | I.V. Ramakrishnan | Scalable data extraction techniques for transforming electronic documents into queriable archives |
US6868411B2 (en) * | 2001-08-13 | 2005-03-15 | Xerox Corporation | Fuzzy text categorizer |
US20050108630A1 (en) * | 2003-11-19 | 2005-05-19 | Wasson Mark D. | Extraction of facts from text |
US20060047691A1 (en) * | 2004-08-31 | 2006-03-02 | Microsoft Corporation | Creating a document index from a flex- and Yacc-generated named entity recognizer |
US20060129843A1 (en) * | 2001-12-19 | 2006-06-15 | Narayan Srinivasa | Method and apparatus for electronically extracting application specific multidimensional information from documents selected from a set of documents electronically extracted from a library of electronically searchable documents |
Family Cites Families (224)
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 |
US5133075A (en) | 1988-12-19 | 1992-07-21 | Hewlett-Packard Company | Method of monitoring changes in attribute values of object in an object-oriented database |
US5440730A (en) | 1990-08-09 | 1995-08-08 | Bell Communications Research, Inc. | Time index access structure for temporal databases having concurrent multiple versions |
CA2048306A1 (en) | 1990-10-02 | 1992-04-03 | Steven P. Miller | Distributed configuration profile for computing system |
US5347653A (en) | 1991-06-28 | 1994-09-13 | Digital Equipment Corporation | System for reconstructing prior versions of indexes using records indicating changes between successive versions of the indexes |
US5694590A (en) | 1991-09-27 | 1997-12-02 | The Mitre Corporation | Apparatus and method for the detection of security violations in multilevel secure databases |
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 |
US7082426B2 (en) | 1993-06-18 | 2006-07-25 | Cnet Networks, Inc. | Content aggregation method and apparatus for an on-line product catalog |
US5519608A (en) | 1993-06-24 | 1996-05-21 | Xerox Corporation | Method for extracting from a text corpus answers to questions stated in natural language by using linguistic analysis and hypothesis generation |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US5680622A (en) | 1994-06-30 | 1997-10-21 | Borland International, Inc. | System and methods for quickly detecting shareability of symbol and type information in header files |
JP2809341B2 (en) | 1994-11-18 | 1998-10-08 | 松下電器産業株式会社 | Information summarizing method, information summarizing device, weighting method, and teletext receiving device. |
US5608903A (en) | 1994-12-15 | 1997-03-04 | Novell, Inc. | Method and apparatus for moving subtrees in a distributed network directory |
US5717911A (en) | 1995-01-23 | 1998-02-10 | Tandem Computers, Inc. | Relational database system and method with high availability compliation of SQL programs |
US5793966A (en) | 1995-12-01 | 1998-08-11 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for creation and maintenance of online services |
US5717951A (en) | 1995-08-07 | 1998-02-10 | Yabumoto; Kan W. | Method for storing and retrieving information on a magnetic storage medium via data blocks of variable sizes |
EP0856175A4 (en) | 1995-08-16 | 2000-05-24 | Univ Syracuse | Multilingual document retrieval system and method using semantic vector matching |
US5701470A (en) | 1995-12-08 | 1997-12-23 | Sun Microsystems, Inc. | System and method for space efficient object locking using a data subarray and pointers |
US5815415A (en) | 1996-01-19 | 1998-09-29 | Bentley Systems, Incorporated | Computer system for portable persistent modeling |
US5802299A (en) | 1996-02-13 | 1998-09-01 | Microtouch Systems, Inc. | Interactive system for authoring hypertext document collections |
US5778378A (en) | 1996-04-30 | 1998-07-07 | International Business Machines Corporation | Object oriented information retrieval framework mechanism |
US5920859A (en) | 1997-02-05 | 1999-07-06 | Idd Enterprises, L.P. | Hypertext document retrieval system and method |
US5819210A (en) | 1996-06-21 | 1998-10-06 | Xerox Corporation | Method of lazy contexted copying during unification |
US6052693A (en) | 1996-07-02 | 2000-04-18 | Harlequin Group Plc | System for assembling large databases through information extracted from text sources |
US5987460A (en) | 1996-07-05 | 1999-11-16 | Hitachi, Ltd. | Document retrieval-assisting method and system for the same and document retrieval service using the same with document frequency and term frequency |
US5819265A (en) | 1996-07-12 | 1998-10-06 | International Business Machines Corporation | Processing names in a text |
US5778373A (en) | 1996-07-15 | 1998-07-07 | At&T Corp | Integration of an information server database schema by generating a translation map from exemplary files |
US5787413A (en) | 1996-07-29 | 1998-07-28 | International Business Machines Corporation | C++ classes for a digital library |
US5826258A (en) | 1996-10-02 | 1998-10-20 | Junglee Corporation | Method and apparatus for structuring the querying and interpretation of semistructured information |
US6285999B1 (en) | 1997-01-10 | 2001-09-04 | The Board Of Trustees Of The Leland Stanford Junior University | Method for node ranking in a linked database |
AUPO525497A0 (en) | 1997-02-21 | 1997-03-20 | Mills, Dudley John | Network-based classified information systems |
US6134555A (en) | 1997-03-10 | 2000-10-17 | International Business Machines Corporation | Dimension reduction using association rules for data mining application |
US5822743A (en) | 1997-04-08 | 1998-10-13 | 1215627 Ontario Inc. | Knowledge-based information retrieval system |
US6038560A (en) | 1997-05-21 | 2000-03-14 | Oracle Corporation | Concept knowledge base search and retrieval system |
US5974254A (en) | 1997-06-06 | 1999-10-26 | National Instruments Corporation | Method for detecting differences between graphical programs |
US5893093A (en) | 1997-07-02 | 1999-04-06 | The Sabre Group, Inc. | Information search and retrieval with geographical coordinates |
US5909689A (en) | 1997-09-18 | 1999-06-01 | Sony Corporation | Automatic update of file versions for files shared by several computers which record in respective file directories temporal information for indicating when the files have been created |
US6073130A (en) | 1997-09-23 | 2000-06-06 | At&T Corp. | Method for improving the results of a search in a structured database |
US6442540B2 (en) | 1997-09-29 | 2002-08-27 | Kabushiki Kaisha Toshiba | Information retrieval apparatus and information retrieval method |
US6018741A (en) | 1997-10-22 | 2000-01-25 | International Business Machines Corporation | Method and system for managing objects in a dynamic inheritance tree |
US6112210A (en) | 1997-10-31 | 2000-08-29 | Oracle Corporation | Apparatus and method for null representation in database object storage |
US5943670A (en) | 1997-11-21 | 1999-08-24 | International Business Machines Corporation | System and method for categorizing objects in combined categories |
US6349275B1 (en) | 1997-11-24 | 2002-02-19 | International Business Machines Corporation | Multiple concurrent language support system for electronic catalogue using a concept based knowledge representation |
US6212526B1 (en) | 1997-12-02 | 2001-04-03 | Microsoft Corporation | Method for apparatus for efficient mining of classification models from databases |
US6094650A (en) | 1997-12-15 | 2000-07-25 | Manning & Napier Information Services | Database analysis using a probabilistic ontology |
US6044366A (en) | 1998-03-16 | 2000-03-28 | Microsoft Corporation | Use of the UNPIVOT relational operator in the efficient gathering of sufficient statistics for data mining |
US6078918A (en) | 1998-04-02 | 2000-06-20 | Trivada Corporation | Online predictive memory |
US6112203A (en) | 1998-04-09 | 2000-08-29 | Altavista Company | Method for ranking documents in a hyperlinked environment using connectivity and selective content analysis |
US6567846B1 (en) | 1998-05-15 | 2003-05-20 | E.Piphany, Inc. | Extensible user interface for a distributed messaging framework in a computer network |
US6122647A (en) | 1998-05-19 | 2000-09-19 | Perspecta, Inc. | Dynamic generation of contextual links in hypertext documents |
US6742003B2 (en) | 2001-04-30 | 2004-05-25 | Microsoft Corporation | Apparatus and accompanying methods for visualizing clusters of data and hierarchical cluster classifications |
US6327574B1 (en) | 1998-07-07 | 2001-12-04 | Encirq Corporation | Hierarchical models of consumer attributes for targeting content in a privacy-preserving manner |
US6240546B1 (en) | 1998-07-24 | 2001-05-29 | International Business Machines Corporation | Identifying date fields for runtime year 2000 system solution process, method and article of manufacture |
AU5181099A (en) | 1998-07-30 | 2000-02-21 | British Telecommunications Public Limited Company | An index to a semi-structured database |
US6665837B1 (en) | 1998-08-10 | 2003-12-16 | Overture Services, Inc. | Method for identifying related pages in a hyperlinked database |
US6694482B1 (en) | 1998-09-11 | 2004-02-17 | Sbc Technology Resources, Inc. | System and methods for an architectural framework for design of an adaptive, personalized, interactive content delivery system |
FR2787957B1 (en) | 1998-12-28 | 2001-10-05 | Inst Nat Rech Inf Automat | PROCESS FOR PROCESSING A REQUEST |
US6572661B1 (en) | 1999-01-11 | 2003-06-03 | Cisco Technology, Inc. | System and method for automated annotation of files |
US6377943B1 (en) | 1999-01-20 | 2002-04-23 | Oracle Corp. | Initial ordering of tables for database queries |
US7003719B1 (en) | 1999-01-25 | 2006-02-21 | West Publishing Company, Dba West Group | System, method, and software for inserting hyperlinks into documents |
US6574635B2 (en) | 1999-03-03 | 2003-06-03 | Siebel Systems, Inc. | Application instantiation based upon attributes and values stored in a meta data repository, including tiering of application layers objects and components |
US6584464B1 (en) | 1999-03-19 | 2003-06-24 | Ask Jeeves, Inc. | Grammar template query system |
US6397228B1 (en) | 1999-03-31 | 2002-05-28 | Verizon Laboratories Inc. | Data enhancement techniques |
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 |
US6721713B1 (en) | 1999-05-27 | 2004-04-13 | Andersen Consulting Llp | Business alliance identification in a web architecture framework |
US6606625B1 (en) | 1999-06-03 | 2003-08-12 | University Of Southern California | Wrapper induction by hierarchical data analysis |
US6711585B1 (en) | 1999-06-15 | 2004-03-23 | Kanisa Inc. | System and method for implementing a knowledge management system |
US6473898B1 (en) | 1999-07-06 | 2002-10-29 | Pcorder.Com, Inc. | Method for compiling and selecting data attributes |
US6873982B1 (en) | 1999-07-16 | 2005-03-29 | International Business Machines Corporation | Ordering of database search results based on user feedback |
EP1072987A1 (en) | 1999-07-29 | 2001-01-31 | International Business Machines Corporation | Geographic web browser and iconic hyperlink cartography |
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 |
US6845354B1 (en) | 1999-09-09 | 2005-01-18 | Institute For Information Industry | Information retrieval system with a neuro-fuzzy structure |
US6754873B1 (en) | 1999-09-20 | 2004-06-22 | Google Inc. | Techniques for finding related hyperlinked documents using link-based analysis |
GB2371901B (en) | 1999-09-21 | 2004-06-23 | Andrew E Borthwick | A probabilistic record linkage model derived from training data |
US6665666B1 (en) | 1999-10-26 | 2003-12-16 | International Business Machines Corporation | System, method and program product for answering questions using a search engine |
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 |
US6804667B1 (en) | 1999-11-30 | 2004-10-12 | Ncr Corporation | Filter for checking for duplicate entries in database |
US6963867B2 (en) | 1999-12-08 | 2005-11-08 | A9.Com, Inc. | Search query processing to provide category-ranked presentation of search results |
US7305380B1 (en) | 1999-12-15 | 2007-12-04 | Google Inc. | Systems and methods for performing in-context searching |
US6865582B2 (en) | 2000-01-03 | 2005-03-08 | Bechtel Bwxt Idaho, Llc | Systems and methods for knowledge discovery in spatial data |
US6606659B1 (en) | 2000-01-28 | 2003-08-12 | Websense, Inc. | System and method for controlling access to internet sites |
US6665659B1 (en) | 2000-02-01 | 2003-12-16 | James D. Logan | Methods and apparatus for distributing and using metadata via the internet |
US6567936B1 (en) | 2000-02-08 | 2003-05-20 | Microsoft Corporation | Data clustering using error-tolerant frequent item sets |
US6886005B2 (en) | 2000-02-17 | 2005-04-26 | E-Numerate Solutions, Inc. | RDL search engine |
US6901403B1 (en) | 2000-03-02 | 2005-05-31 | Quovadx, Inc. | XML presentation of general-purpose data sources |
US6311194B1 (en) | 2000-03-15 | 2001-10-30 | Taalee, Inc. | System and method for creating a semantic web and its applications in browsing, searching, profiling, personalization and advertising |
US6738767B1 (en) | 2000-03-20 | 2004-05-18 | International Business Machines Corporation | System and method for discovering schematic structure in hypertext documents |
US6502102B1 (en) | 2000-03-27 | 2002-12-31 | Accenture Llp | System, method and article of manufacture for a table-driven automated scripting architecture |
US6643641B1 (en) | 2000-04-27 | 2003-11-04 | Russell Snyder | Web search engine with graphic snapshots |
EP1156430A2 (en) | 2000-05-17 | 2001-11-21 | Matsushita Electric Industrial Co., Ltd. | Information retrieval system |
US6957213B1 (en) | 2000-05-17 | 2005-10-18 | Inquira, Inc. | Method of utilizing implicit references to answer a query |
US7062483B2 (en) | 2000-05-18 | 2006-06-13 | Endeca Technologies, Inc. | Hierarchical data-driven search and navigation system and method for information retrieval |
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 |
US7028250B2 (en) | 2000-05-25 | 2006-04-11 | Kanisa, Inc. | System and method for automatically classifying text |
US6487495B1 (en) | 2000-06-02 | 2002-11-26 | Navigation Technologies Corporation | Navigation applications using related location-referenced keywords |
US6963876B2 (en) | 2000-06-05 | 2005-11-08 | International Business Machines Corporation | System and method for searching extended regular expressions |
US6745189B2 (en) | 2000-06-05 | 2004-06-01 | International Business Machines Corporation | System and method for enabling multi-indexing of objects |
US20020042707A1 (en) | 2000-06-19 | 2002-04-11 | Gang Zhao | Grammar-packaged parsing |
US7162499B2 (en) | 2000-06-21 | 2007-01-09 | Microsoft Corporation | Linked value replication |
MXPA03000110A (en) | 2000-06-22 | 2006-06-08 | Mayer Yaron | System and method for searching, finding and contacting dates on the internet in instant messaging networks. |
US7003506B1 (en) | 2000-06-23 | 2006-02-21 | Microsoft Corporation | Method and system for creating an embedded search link document |
US7080085B1 (en) | 2000-07-12 | 2006-07-18 | International Business Machines Corporation | System and method for ensuring referential integrity for heterogeneously scoped references in an information management system |
US6728728B2 (en) * | 2000-07-24 | 2004-04-27 | Israel Spiegler | Unified binary model and methodology for knowledge representation and for data and information mining |
US7146536B2 (en) | 2000-08-04 | 2006-12-05 | Sun Microsystems, Inc. | Fact collection for product knowledge management |
US7080073B1 (en) | 2000-08-18 | 2006-07-18 | Firstrain, Inc. | Method and apparatus for focused crawling |
US6556991B1 (en) | 2000-09-01 | 2003-04-29 | E-Centives, Inc. | Item name normalization |
US6823495B1 (en) | 2000-09-14 | 2004-11-23 | Microsoft Corporation | Mapping tool graphical user interface |
US6832218B1 (en) | 2000-09-22 | 2004-12-14 | International Business Machines Corporation | System and method for associating search results |
US7493308B1 (en) | 2000-10-03 | 2009-02-17 | A9.Com, Inc. | Searching documents using a dimensional database |
WO2002044949A2 (en) | 2000-11-28 | 2002-06-06 | Everypath, Inc. | Minimal identification of features |
US7013308B1 (en) | 2000-11-28 | 2006-03-14 | Semscript Ltd. | Knowledge storage and retrieval system and method |
US8402068B2 (en) * | 2000-12-07 | 2013-03-19 | Half.Com, Inc. | System and method for collecting, associating, normalizing and presenting product and vendor information on a distributed network |
JP2002230035A (en) | 2001-01-05 | 2002-08-16 | Internatl Business Mach Corp <Ibm> | Information arranging method, information processor, information processing system, storage medium and program transmitting device |
US6693651B2 (en) | 2001-02-07 | 2004-02-17 | International Business Machines Corporation | Customer self service iconic interface for resource search results display and selection |
US7143099B2 (en) | 2001-02-08 | 2006-11-28 | Amdocs Software Systems Limited | Historical data warehousing system |
WO2002073451A2 (en) | 2001-03-13 | 2002-09-19 | Intelligate Ltd. | Dynamic natural language understanding |
US6820081B1 (en) | 2001-03-19 | 2004-11-16 | Attenex Corporation | System and method for evaluating a structured message store for message redundancy |
US20020147738A1 (en) | 2001-04-06 | 2002-10-10 | Reader Scot A. | Method and appratus for finding patent-relevant web documents |
CN100409675C (en) | 2001-04-12 | 2008-08-06 | 皇家菲利浦电子有限公司 | Method and system for registering user preference |
US20020169770A1 (en) | 2001-04-27 | 2002-11-14 | Kim Brian Seong-Gon | Apparatus and method that categorize a collection of documents into a hierarchy of categories that are defined by the collection of documents |
US7020662B2 (en) | 2001-05-29 | 2006-03-28 | Sun Microsystems, Inc. | Method and system for determining a directory entry's class of service based on the value of a specifier in the entry |
WO2003001413A1 (en) | 2001-06-22 | 2003-01-03 | Nosa Omoigui | System and method for knowledge retrieval, management, delivery and presentation |
CN1310172C (en) | 2001-07-26 | 2007-04-11 | 国际商业机器公司 | Data processing method, data processing system and program |
EP1428139B1 (en) | 2001-08-14 | 2015-06-03 | Microsoft Technology Licensing, LLC | System and method for extracting content for submission to a search engine |
US6607151B2 (en) | 2001-08-16 | 2003-08-19 | Morris Samelson | Ultra fine dead sea mineral compound and method of manufacture |
US7386832B2 (en) | 2001-08-31 | 2008-06-10 | Siebel Systems, Inc. | Configurator using structure to provide a user interface |
US7058653B2 (en) | 2001-09-17 | 2006-06-06 | Ricoh Company, Ltd. | Tree system diagram output method, computer program and recording medium |
US7403938B2 (en) | 2001-09-24 | 2008-07-22 | Iac Search & Media, Inc. | Natural language query processing |
US7020641B2 (en) | 2001-10-22 | 2006-03-28 | Sun Microsystems, Inc. | Method, system, and program for maintaining a database of data objects |
US7197449B2 (en) | 2001-10-30 | 2007-03-27 | Intel Corporation | Method for extracting name entities and jargon terms using a suffix tree data structure |
CN100461156C (en) * | 2001-11-09 | 2009-02-11 | 无锡永中科技有限公司 | Integrated data processing system |
JP3931214B2 (en) | 2001-12-17 | 2007-06-13 | 日本アイ・ビー・エム株式会社 | Data analysis apparatus and program |
US7096231B2 (en) | 2001-12-28 | 2006-08-22 | American Management Systems, Inc. | Export engine which builds relational database directly from object model |
US20030149567A1 (en) | 2002-02-04 | 2003-08-07 | Tony Schmitz | Method and system for using natural language in computer resource utilization analysis via a communications network |
CA2475267C (en) | 2002-02-04 | 2014-08-05 | Cataphora, Inc. | A method and apparatus for sociological data mining |
US7421660B2 (en) | 2003-02-04 | 2008-09-02 | Cataphora, Inc. | Method and apparatus to visually present discussions for data mining purposes |
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 |
US7165024B2 (en) | 2002-02-22 | 2007-01-16 | Nec Laboratories America, Inc. | Inferring hierarchical descriptions of a set of documents |
JP4098539B2 (en) | 2002-03-15 | 2008-06-11 | 富士通株式会社 | Profile information recommendation method, program, and apparatus |
US7043521B2 (en) | 2002-03-21 | 2006-05-09 | Rockwell Electronic Commerce Technologies, Llc | Search agent for searching the internet |
US6857053B2 (en) | 2002-04-10 | 2005-02-15 | International Business Machines Corporation | Method, system, and program for backing up objects by creating groups of objects |
TWI256562B (en) | 2002-05-03 | 2006-06-11 | Ind Tech Res Inst | Method for named-entity recognition and verification |
US6963880B1 (en) | 2002-05-10 | 2005-11-08 | Oracle International Corporation | Schema evolution of complex objects |
US7003522B1 (en) | 2002-06-24 | 2006-02-21 | Microsoft Corporation | System and method for incorporating smart tags in online content |
US20040003067A1 (en) | 2002-06-27 | 2004-01-01 | Daniel Ferrin | System and method for enabling a user interface with GUI meta data |
GB0215464D0 (en) | 2002-07-04 | 2002-08-14 | Hewlett Packard Co | Combining data descriptions |
JP2005538437A (en) | 2002-08-22 | 2005-12-15 | エイジェンシー フォー サイエンス, テクノロジー アンド リサーチ | Prediction with likelihood set from emerging patterns |
US20040059726A1 (en) | 2002-09-09 | 2004-03-25 | Jeff Hunter | Context-sensitive wordless search |
US20040064447A1 (en) | 2002-09-27 | 2004-04-01 | Simske Steven J. | System and method for management of synonymic searching |
US6886010B2 (en) | 2002-09-30 | 2005-04-26 | The United States Of America As Represented By The Secretary Of The Navy | Method for data and text mining and literature-based discovery |
US7096217B2 (en) | 2002-10-31 | 2006-08-22 | International Business Machines Corporation | Global query correlation attributes |
US7277879B2 (en) | 2002-12-17 | 2007-10-02 | Electronic Data Systems Corporation | Concept navigation in data storage systems |
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 |
US20040122846A1 (en) | 2002-12-19 | 2004-06-24 | Ibm Corporation | Fact verification system |
US7107528B2 (en) | 2002-12-20 | 2006-09-12 | International Business Machines Corporation | Automatic completion of dates |
US7472182B1 (en) | 2002-12-31 | 2008-12-30 | Emc Corporation | Data collection policy for storage devices |
GB0304639D0 (en) | 2003-02-28 | 2003-04-02 | Kiq Ltd | Classification using re-sampling of probability estimates |
US7020666B2 (en) * | 2003-03-07 | 2006-03-28 | Microsoft Corporation | System and method for unknown type serialization |
US7051023B2 (en) | 2003-04-04 | 2006-05-23 | Yahoo! Inc. | Systems and methods for generating concept units from search queries |
EP1629359A4 (en) | 2003-04-07 | 2008-01-09 | Sevenecho Llc | Method, system and software for digital media narrative personalization |
US20040243552A1 (en) | 2003-05-30 | 2004-12-02 | Dictaphone Corporation | Method, system, and apparatus for viewing data |
JP2004362223A (en) | 2003-06-04 | 2004-12-24 | Hitachi Ltd | Information mining system |
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 |
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 |
US7739588B2 (en) | 2003-06-27 | 2010-06-15 | Microsoft Corporation | Leveraging markup language data for semantically labeling text strings and data and for providing actions based on semantically labeled text strings and data |
WO2005008358A2 (en) | 2003-07-22 | 2005-01-27 | Kinor Technologies Inc. | Information access using ontologies |
US20060242180A1 (en) | 2003-07-23 | 2006-10-26 | Graf James A | Extracting data from semi-structured text documents |
US7895221B2 (en) | 2003-08-21 | 2011-02-22 | Idilia Inc. | Internet searching using semantic disambiguation and expansion |
US7496560B2 (en) | 2003-09-23 | 2009-02-24 | Amazon Technologies, Inc. | Personalized searchable library with highlighting capabilities |
US7158980B2 (en) | 2003-10-02 | 2007-01-02 | Acer Incorporated | Method and apparatus for computerized extracting of scheduling information from a natural language e-mail |
AU2003290397A1 (en) | 2003-10-15 | 2005-04-27 | Dharamdas Gautam Goradia | Interactive wisdom system |
KR100533810B1 (en) | 2003-10-16 | 2005-12-07 | 한국전자통신연구원 | Semi-Automatic Construction Method for Knowledge of Encyclopedia Question Answering System |
GB0325626D0 (en) | 2003-11-03 | 2003-12-10 | Infoshare Ltd | Data aggregation |
US7512553B2 (en) | 2003-12-05 | 2009-03-31 | International Business Machines Corporation | System for automated part-number mapping |
US20050149851A1 (en) | 2003-12-31 | 2005-07-07 | Google Inc. | Generating hyperlinks and anchor text in HTML and non-HTML documents |
US8150824B2 (en) | 2003-12-31 | 2012-04-03 | Google Inc. | Systems and methods for direct navigation to specific portion of target document |
US7424467B2 (en) | 2004-01-26 | 2008-09-09 | International Business Machines Corporation | Architecture for an indexer with fixed width sort and variable width sort |
EP1716511A1 (en) | 2004-02-20 | 2006-11-02 | Dow Jones Reuters Business Interactive, LLC | Intelligent search and retrieval system and method |
US7725498B2 (en) | 2004-04-22 | 2010-05-25 | International Business Machines Corporation | Techniques for identifying mergeable data |
US8051207B2 (en) | 2004-06-25 | 2011-11-01 | Citrix Systems, Inc. | Inferring server state in s stateless communication protocol |
US20060036504A1 (en) | 2004-08-11 | 2006-02-16 | Allocca William W | Dynamically classifying items for international delivery |
US7809695B2 (en) | 2004-08-23 | 2010-10-05 | Thomson Reuters Global Resources | Information retrieval systems with duplicate document detection and presentation functions |
US20060053171A1 (en) | 2004-09-03 | 2006-03-09 | Biowisdom Limited | System and method for curating one or more multi-relational ontologies |
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 |
US20060074910A1 (en) | 2004-09-17 | 2006-04-06 | Become, Inc. | Systems and methods of retrieving topic specific information |
WO2006036781A2 (en) | 2004-09-22 | 2006-04-06 | Perfect Market Technologies, Inc. | Search engine using user intent |
US7809763B2 (en) | 2004-10-15 | 2010-10-05 | Oracle International Corporation | Method(s) for updating database object metadata |
US7822768B2 (en) | 2004-11-23 | 2010-10-26 | International Business Machines Corporation | System and method for automating data normalization using text analytics |
US9137115B2 (en) | 2004-12-06 | 2015-09-15 | Bmc Software, Inc. | System and method for resource reconciliation in an enterprise management system |
US20060143227A1 (en) | 2004-12-27 | 2006-06-29 | Helm Martin W | System and method for persisting software objects |
US8719779B2 (en) | 2004-12-28 | 2014-05-06 | Sap Ag | Data object association based on graph theory techniques |
US7769579B2 (en) * | 2005-05-31 | 2010-08-03 | Google Inc. | Learning facts from semi-structured text |
US7672971B2 (en) * | 2006-02-17 | 2010-03-02 | Google Inc. | Modular architecture for entity normalization |
US7685136B2 (en) | 2005-01-12 | 2010-03-23 | International Business Machines Corporation | Method, system and program product for managing document summary information |
US9208229B2 (en) | 2005-03-31 | 2015-12-08 | Google Inc. | Anchor text summarization for corroboration |
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 |
US20060238919A1 (en) | 2005-04-20 | 2006-10-26 | The Boeing Company | Adaptive data cleaning |
US20060248456A1 (en) | 2005-05-02 | 2006-11-02 | Ibm Corporation | Assigning a publication date for at least one electronic document |
US20060259462A1 (en) | 2005-05-12 | 2006-11-16 | Sybase, Inc. | System and Methodology for Real-time Content Aggregation and Syndication |
US7590647B2 (en) | 2005-05-27 | 2009-09-15 | Rage Frameworks, Inc | Method for extracting, interpreting and standardizing tabular data from unstructured documents |
US20060277169A1 (en) * | 2005-06-02 | 2006-12-07 | Lunt Tracy T | Using the quantity of electronically readable text to generate a derivative attribute for an electronic file |
US7630977B2 (en) | 2005-06-29 | 2009-12-08 | Xerox Corporation | Categorization including dependencies between different category systems |
US20070005593A1 (en) | 2005-06-30 | 2007-01-04 | Microsoft Corporation | Attribute-based data retrieval and association |
US8666928B2 (en) | 2005-08-01 | 2014-03-04 | Evi Technologies Limited | Knowledge repository |
US7797282B1 (en) | 2005-09-29 | 2010-09-14 | Hewlett-Packard Development Company, L.P. | System and method for modifying a training set |
US7493317B2 (en) | 2005-10-20 | 2009-02-17 | Omniture, Inc. | Result-based triggering for presentation of online content |
US7730013B2 (en) | 2005-10-25 | 2010-06-01 | International Business Machines Corporation | System and method for searching dates efficiently in a collection of web documents |
KR100755678B1 (en) | 2005-10-28 | 2007-09-05 | 삼성전자주식회사 | Apparatus and method for detecting named entity |
US7574449B2 (en) | 2005-12-02 | 2009-08-11 | Microsoft Corporation | Content matching |
US7454398B2 (en) | 2006-02-17 | 2008-11-18 | Google Inc. | Support for object search |
US7774328B2 (en) | 2006-02-17 | 2010-08-10 | Google Inc. | Browseable fact repository |
US7991797B2 (en) | 2006-02-17 | 2011-08-02 | Google Inc. | ID persistence through normalization |
US8954426B2 (en) | 2006-02-17 | 2015-02-10 | Google Inc. | Query language |
US7555471B2 (en) | 2006-01-27 | 2009-06-30 | Google Inc. | Data object visualization |
US8260785B2 (en) | 2006-02-17 | 2012-09-04 | Google Inc. | Automatic object reference identification and linking in a browseable fact repository |
US8700568B2 (en) * | 2006-02-17 | 2014-04-15 | Google Inc. | Entity normalization via name normalization |
US9286404B2 (en) | 2006-06-28 | 2016-03-15 | Nokia Technologies Oy | Methods of systems using geographic meta-metadata in information retrieval and document displays |
US7685201B2 (en) | 2006-09-08 | 2010-03-23 | Microsoft Corporation | Person disambiguation using name entity extraction-based clustering |
US8458207B2 (en) | 2006-09-15 | 2013-06-04 | Microsoft Corporation | Using anchor text to provide context |
US8316007B2 (en) | 2007-06-28 | 2012-11-20 | Oracle International Corporation | Automatically finding acronyms and synonyms in a corpus |
-
2007
- 2007-07-23 US US11/781,891 patent/US7970766B1/en active Active
-
2011
- 2011-06-28 US US13/171,296 patent/US20120136859A1/en not_active Abandoned
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6868411B2 (en) * | 2001-08-13 | 2005-03-15 | Xerox Corporation | Fuzzy text categorizer |
US20060129843A1 (en) * | 2001-12-19 | 2006-06-15 | Narayan Srinivasa | Method and apparatus for electronically extracting application specific multidimensional information from documents selected from a set of documents electronically extracted from a library of electronically searchable documents |
US20040167907A1 (en) * | 2002-12-06 | 2004-08-26 | Attensity Corporation | Visualization of integrated structured data and extracted relational facts from free text |
US20040167911A1 (en) * | 2002-12-06 | 2004-08-26 | Attensity Corporation | Methods and products for integrating mixed format data including the extraction of relational facts from free text |
US20050055365A1 (en) * | 2003-09-09 | 2005-03-10 | I.V. Ramakrishnan | Scalable data extraction techniques for transforming electronic documents into queriable archives |
US20050108630A1 (en) * | 2003-11-19 | 2005-05-19 | Wasson Mark D. | Extraction of facts from text |
US20060047691A1 (en) * | 2004-08-31 | 2006-03-02 | Microsoft Corporation | Creating a document index from a flex- and Yacc-generated named entity recognizer |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160092475A1 (en) * | 2014-09-26 | 2016-03-31 | Oracle International Corporation | Automated entity correlation and classification across heterogeneous datasets |
US10210246B2 (en) | 2014-09-26 | 2019-02-19 | Oracle International Corporation | Techniques for similarity analysis and data enrichment using knowledge sources |
US10296192B2 (en) | 2014-09-26 | 2019-05-21 | Oracle International Corporation | Dynamic visual profiling and visualization of high volume datasets and real-time smart sampling and statistical profiling of extremely large datasets |
US10891272B2 (en) | 2014-09-26 | 2021-01-12 | Oracle International Corporation | Declarative language and visualization system for recommended data transformations and repairs |
US10915233B2 (en) * | 2014-09-26 | 2021-02-09 | Oracle International Corporation | Automated entity correlation and classification across heterogeneous datasets |
US10976907B2 (en) | 2014-09-26 | 2021-04-13 | Oracle International Corporation | Declarative external data source importation, exportation, and metadata reflection utilizing http and HDFS protocols |
US11379506B2 (en) | 2014-09-26 | 2022-07-05 | Oracle International Corporation | Techniques for similarity analysis and data enrichment using knowledge sources |
US11693549B2 (en) | 2014-09-26 | 2023-07-04 | Oracle International Corporation | Declarative external data source importation, exportation, and metadata reflection utilizing HTTP and HDFS protocols |
US20180173694A1 (en) * | 2016-12-21 | 2018-06-21 | Industrial Technology Research Institute | Methods and computer systems for named entity verification, named entity verification model training, and phrase expansion |
US10885056B2 (en) | 2017-09-29 | 2021-01-05 | Oracle International Corporation | Data standardization techniques |
US10936599B2 (en) | 2017-09-29 | 2021-03-02 | Oracle International Corporation | Adaptive recommendations |
US11500880B2 (en) | 2017-09-29 | 2022-11-15 | Oracle International Corporation | Adaptive recommendations |
Also Published As
Publication number | Publication date |
---|---|
US7970766B1 (en) | 2011-06-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7970766B1 (en) | Entity type assignment | |
US9558186B2 (en) | Unsupervised extraction of facts | |
Zhuge | The web resource space model | |
Wang et al. | A machine learning based approach for table detection on the web | |
US7912816B2 (en) | Adaptive archive data management | |
US8244689B2 (en) | Attribute entropy as a signal in object normalization | |
US7464090B2 (en) | Object categorization for information extraction | |
US9208229B2 (en) | Anchor text summarization for corroboration | |
US20080147642A1 (en) | System for discovering data artifacts in an on-line data object | |
US20090327230A1 (en) | Structured and unstructured data models | |
US20080147588A1 (en) | Method for discovering data artifacts in an on-line data object | |
US20080147641A1 (en) | Method for prioritizing search results retrieved in response to a computerized search query | |
Roopak et al. | OntoKnowNHS: ontology driven knowledge centric novel hybridised semantic scheme for image recommendation using knowledge graph | |
US20100138414A1 (en) | Methods and systems for associative search | |
Hernandez et al. | A semantic focused web crawler based on a knowledge representation schema | |
Nashipudimath et al. | An efficient integration and indexing method based on feature patterns and semantic analysis for big data | |
CN115210705A (en) | Vector embedding model for relational tables with invalid or equivalent values | |
Oo | Pattern discovery using association rule mining on clustered data | |
CN114880483A (en) | Metadata knowledge graph construction method, storage medium and system | |
Safaei et al. | Multidimensional indexing technique for medical images retrieval | |
CN114648121A (en) | Data processing method and device, electronic equipment and storage medium | |
Do et al. | Toward a statistical data integration environment: the role of semantic metadata | |
US20230170099A1 (en) | Pharmaceutical process | |
US20230409624A1 (en) | Multi-modal hierarchical semantic search engine | |
Yu et al. | Web of Conferences: A Conference Knowledge Graph |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |