Abstract: A repository contains objects including facts about entities. Some objects might be associated with the same entity. An object merge engine identifies a set of merge candidate objects. A grouping module groups the merge candidate objects based on the values of facts included in the objects. An object comparison module compares pairs of objects in each group to identify evidence for and/or against merging the pair. Evidence for merging the pair exists if, e.g., the objects have a type in common or share an uncommon fact. Evidence against merging the pair exists if, e.g., the objects have differing singleton attributes. A graph generation module generates graphs describing the evidence for and/or against merging the pair. A merging module analyzes the graphs and merges objects associated with the same entity. The merged objects are stored in the repository.

Abstract: A fact repository stores objects. Each object includes a collection of facts, where a fact comprises an attribute and a value. A set of objects from the fact repository are designated for analysis. The presentation engine presents the facts of the objects in a user interface (UI) having a table. Through manipulation of the UI, an end-user can add or remove facts from the table, and sort the table based on the values of particular facts. The presentation engine also presents the facts of the objects in a UI having a graph. Through manipulation of the UI, the end-user can add or remove facts from the graph, and can sort the facts shown in the graph based on values that are shown, or not shown, in the graph. The presentation engine can further present the facts of the objects in UIs including maps and timelines.

Abstract: A set of objects having facts is established. Facts of objects having positions in an order are identified. Some facts explicitly describe the positions in the linear order, while are facts do not explicitly describe the positions. The facts are presented in the order on a linear graph, such as a timeline. Facts of the objects describing geographic positions are presented on a map.

Abstract: A fact repository stores objects. Each object includes a collection of facts, where a fact comprises an attribute and a value. A set of objects from the fact repository are designated for analysis. The presentation engine presents the facts of the objects in a user interface (UI) having a table. Through manipulation of the UI, an end-user can add or remove facts from the table, and sort the table based on the values of particular facts. The presentation engine also presents the facts of the objects in a UI having a graph. Through manipulation of the UI, the end-user can add or remove facts from the graph, and can sort the facts shown in the graph based on values that are shown, or not shown, in the graph. The presentation engine can further present the facts of the objects in UIs including maps and timelines.

Abstract: A fact repository stores objects. Each object includes a collection of facts, where a fact comprises an attribute and a value. A set of objects from the fact repository are designated for analysis. The presentation engine presents the facts of the objects in a user interface (UI) having a table. Through manipulation of the UI, an end-user can add or remove facts from the table, and sort the table based on the values of particular facts. The presentation engine also presents the facts of the objects in a UI having a graph. Through manipulation of the UI, the end-user can add or remove facts from the graph, and can sort the facts shown in the graph based on values that are shown, or not shown, in the graph. The presentation engine can further present the facts of the objects in UIs including maps and timelines.

Abstract: A fact repository supports searches of facts relevant to search queries comprising keywords and phrases. The repository responds to requests from object requesters by sending a feed containing matching facts from the repository and, optionally, facts associated with the same object as the matching facts.

Abstract: A presentation engine presents facts in a UI having a graph. Through manipulation of the UI, an end-user can add or remove facts from the graph, and can sort the facts shown in the graph based on values that are shown, or not shown, in the graph. The presentation engine determines a graph type that best facilitates interpretation of the facts by the end-user and automatically creates a graph of that type. Possible graph types include bar graphs, scatter plots, timelines, and maps.

Abstract: A fact repository stores objects. Each object includes a collection of facts, where a fact comprises an attribute and a value. A set of objects from the fact repository are designated for analysis. The presentation engine presents the facts of the objects in a user interface (UI) having a table. Through manipulation of the UI, an end-user can add or remove facts from the table, and sort the table based on the values of particular facts. The presentation engine also presents the facts of the objects in a UI having a graph. Through manipulation of the UI, the end-user can add or remove facts from the graph, and can sort the facts shown in the graph based on values that are shown, or not shown, in the graph. The presentation engine can further present the facts of the objects in UIs including maps and timelines.

Abstract: A set of objects having facts is established. Facts of objects having positions in a order are identified. Some facts explicitly describe the positions in the linear order, while are facts do not explicitly describe the positions. The facts are presented in the order on a linear graph, such as a timeline. Facts of the objects describing geographic positions are presented on a map.

Abstract: A fact repository stores objects. Each object includes a collection of facts, where a fact comprises an attribute and a value. An object access module receives objects from the fact repository. The objects can result from multiple different queries executed against the fact repository. A user interface (UI) generation module provides a UI enabling an end-user to designate objects from multiple different queries for subsequent analysis by storing the objects in a virtual collection.