Abstract: A system for question answering (QA) documents data ingestion decides to ingest the documents data through a first plurality of sub-pipelines including a first sub-pipeline having a first set of engines and a second sub-pipeline having a second set of engines being independent from the first set of engines. The system determines a subset of the documents data and decides to ingest the subset through a second plurality of sub-pipelines including a third sub-pipeline having a third set of engines and a fourth sub-pipeline having a fourth set of engines being independent from the third set of engines. A set of engines of the second plurality of sub-pipelines and a set of engines of the first plurality of sub-pipelines are in a common class. The system selects output data from the second plurality of sub-pipelines over corresponding output data from the first plurality of sub-pipelines and generates a knowledge base.

Abstract: A system for handling a graphical representation of data associated with a question answering (QA) input document includes a memory having instructions therein and includes at least one processor in communication with the memory. The at least one processor is configured to execute the instructions to derive, at least from a portion of the QA input document, first metadata regarding a context of the graphical representation of data. The at least one processor is also configured to execute the instructions to derive, at least from a portion of the graphical representation of data, tabular data. The at least one processor is also configured to execute the instructions to determine, at least in part by comparing at least a portion of the first metadata to existing table annotations from a QA knowledge base, how to incorporate the tabular data into the QA knowledge base.

Abstract: A method trains an artificial intelligence system to respond to a complex query. A query/answer (Q/A) system sends a first query to an information server, where the first query is a query about a first topic with regard to a first entity, and where the information server provides access to unstructured information sources. In response to receiving a negative response to the first query for the first entity, the Q/A system sends variations of the first query and a second query about a second topic to the information server. The Q/A system identifies a pattern in the table of information in order to create the answer to the first query for the first entity. The Q/A system then trains an artificial intelligence system to respond to a complex query about the first entity with information in the table of information.

Abstract: A question answering (QA) system comprising memory for storing instructions, and a processor configured to execute the instructions to ingest source documents that include structured data and unstructured data to create a knowledge base, wherein the unstructured data includes table data; create table annotations to represent the table data; store the ingested structured data, unstructured data, and the table annotations in the knowledge base; and determine answers to questions using the knowledge base.

Abstract: A method of augmenting a knowledge graph includes obtaining the knowledge graph, which includes entities and relationships between the entities defining respective edges, clustering the entities into knowledge domains using semantic distances determined between the entities and a threshold on the semantic distances, identifying strengths of the relationships between adjacent entities in the knowledge graph, creating knowledge chains from node pairs in the knowledge graph, including generating a minimum spanning tree using the strengths of the relationships, pruning edges from the knowledge chain using a threshold on weights corresponding to the edges, defining a first knowledge index for each of the knowledge chains, defining a second knowledge index for each of the knowledge domains, and defining a third knowledge index for the knowledge graph as a harmonic mean of a sum of the first knowledge indexes and a sum of the second knowledge indexes.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.

Abstract: Aspects of processing misaligned annotations include receiving a tokenized document and offset annotation file at a processor. The tokenized document includes a source document and corresponding tokens resulting from a low-level segmentation process. Annotations from the annotation file are applied, in conjunction with tokenization rules, to the source document, and a misalignment responsive to the applying is determined. If the misalignment is caused by an offset mismatch, an offset number of characters between the position counts in the annotation file and the source document is calculated, and the position count in the annotation file is adjusted to coincide with the position count in the source document. If the misalignment is not caused by an offset mismatch, a current position count in the source document is reset to a position count of a previous location in which a most recent alignment between the annotation file and the source document was ascertained.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.

Abstract: Aspects of processing misaligned annotations include receiving a tokenized document and offset annotation file at a processor. The tokenized document includes a source document and corresponding tokens resulting from a low-level segmentation process. Annotations from the annotation file are applied, in conjunction with tokenization rules, to the source document, and a misalignment responsive to the applying is determined. If the misalignment is caused by an offset mismatch, an offset number of characters between the position counts in the annotation file and the source document is calculated, and the position count in the annotation file is adjusted to coincide with the position count in the source document. If the misalignment is not caused by an offset mismatch, a current position count in the source document is reset to a position count of a previous location in which a most recent alignment between the annotation file and the source document was ascertained.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.

Abstract: Aspects include creating a profile for a user from user account data and a user activity log, searching an indexed repository for keywords matching elements from the user account data and the user activity log, and retrieving documents from the indexed repository that are identified based on the searching. Aspects further include creating a custom portal for the user that includes the documents.