# Patent

## Title
Method of answering questions and scoring answers using structured knowledge mined from a corpus of data

## Abstract

In a method of answering questions and scoring answers, a title and at least one topical field are identified for a document. A field name and field content associated with the topical field is identified, and a title-oriented document is created by combining the title, the field name, and the field content associated with the topical field. For each title-oriented document, a term in the title is matched to previously established categories to produce a title concept identifier. The topical field is synthesized to produce a field concept identifier and a field content concept identifier. A question is received. The question topic term and the question content identifier are used to identify at least one question-matching relation instance. The title concept identifier of each question-matching relation instance is identified as a candidate answer to the question. Each candidate answer and a corresponding answer score is output.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a Continuation of U.S. application Ser. No. 13/710,509 filed Dec. 11, 2012, the entire teachings of which are incorporated herein by reference, in their entirety.


BACKGROUND
The present disclosure relates generally to document management software and question answer generation. Specifically, this disclosure provides for the conversion of unstructured data into structured data. The structured data is used to provide a score for an answer to a question based on instances that an entry appears in the unstructured document.
Structured knowledge bases may provide precise answers to questions. However, they are expensive to construct because people normally must manually code them. Embodiments herein provide a system and method for automatically constructing structured knowledge bases that can be used to answer questions precisely. According to embodiments herein, the structured knowledge bases may be constructed automatically from a natural language corpus, saving much time and expense, yet providing precise answers.
SUMMARY
According to an embodiment herein, a method of answering questions is disclosed. According to the method, a question is received into a computerized question-answer system operating on a computerized device. A plurality of title-oriented documents is automatically constructed by the computerized device from a corpus of data. The corpus of data comprises natural language documents. Each title-oriented document comprises a title and at least one topical field. The topical field comprises a field name and field content associated with the topical field of at least one document in the corpus of data. At least one relation instance is automatically created using the computerized device by combining a field identifier for the topical field, a title concept identifier, and a corresponding field content concept identifier. Terms in the question are analyzed, using the computerized device, to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The question topic term and the question content identifier are automatically compared to the at least one relation instance, using the computerized device, to identify at least one question-matching relation instance. The computerized device automatically generates at least one answer to the question by identifying the title concept identifier of each question-matching relation instance as a candidate answer to the question.
According to another embodiment herein, a method of answering questions and scoring answers is disclosed. According to the method, a title and at least one topical field is identified for at least a portion of at least one document in a grouping of documents. A field name and field content associated with the topical field are identified. At least one title-oriented document is created by combining the title, the field name, and the field content associated with the at least one topical field of the at least a portion of the at least one document. For each title-oriented document, at least one term in the title that corresponds to previously established categories is identified to produce at least one title concept identifier. The topical field is synthesized to produce at least one field concept identifier and at least one field content concept identifier from the previously established categories. At least one relation instance is created by combining, for each field concept identifier, a corresponding title concept identifier of the at least one title concept identifier and a corresponding field content concept identifier of the at least one field content concept identifier. A count for each relation instance is calculated based on a number of occurrences of the title concept identifier and the field content concept identifier within a corresponding one of the at least one documents in the grouping of documents. The count is included with each relation instance. A question is received. The terms in the question are analyzed to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The question topic term and the question content identifier are compared to at least one of the at least one relation instance to identify at least one question-matching relation instance. The title concept identifier of each question-matching relation instance is identified as a candidate answer to the question. Each count within each relation instance corresponding to each candidate answer is added to provide an answer score for each candidate answer. Each candidate answer and a corresponding answer score are output.
According to another embodiment herein, a method of scoring answers to questions in a question-answering system is disclosed. A question is received into a computerized question-answer system operating on a computerized device. A plurality of title-oriented documents is automatically constructed by the computerized device from a corpus of data. The corpus of data comprises natural language documents. Each title-oriented document comprises a title and at least one topical field. The topical field comprises a field name and field content associated with the topical field of at least one document in the corpus of data. At least one relation instance is automatically created using the computerized device by combining a field identifier for the topical field, a title concept identifier, and a corresponding field content concept identifier. A count for each relation instance is automatically calculated, using the computerized device, based on the number of occurrences of the title concept identifier and the field content concept identifier within a corresponding one of the at least one documents. Terms in the question are analyzed, using the computerized device, to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The question topic term and the question content identifier are automatically compared to at least one of the at least one relation instance, using the computerized device, to identify at least one question-matching relation instance. The computerized device automatically generates at least one answer to the question by identifying the title concept identifier of each question-matching relation instance as a candidate answer to the question. The computerized device generates a score for the candidate answers by adding each count within each relation instance corresponding to each candidate answer.
According to another embodiment herein, a computer-implemented method for automatically generating answers to questions is disclosed. According to the method, a title and at least one topical field for at least a portion of at least one document in a corpus of data comprising natural language documents is identified using a computerized device. A plurality of title-oriented documents is constructed from the corpus of data, by the computerized device. Each title-oriented document comprises a title and at least one topical field. The topical field comprises a field name and field content associated with the topical field of the at least one document in the corpus of data. The computerized device constructs a structured knowledge base from the plurality of title-oriented documents. The structured knowledge base comprises at least one relation instance comprising a field identifier for the topical field, the title concept identifier, and a corresponding field content concept identifier. A question to be answered by a Question Answering (QA) system is provided to a processor of the computerized device. The processor analyzes terms in the question to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The processor creates a collection of candidate answers to the question from the structured knowledge base.
According to another embodiment herein, a computerized device is disclosed. The computerized device includes a processor comprising a question-answer system performing a plurality of question answering processes, a user interface operatively connected to the processor that receives a question into the question-answer system, and a tangible storage device operatively connected to the processor storing a corpus of data comprising a plurality of natural language documents. The processor automatically constructs a plurality of title-oriented documents from the corpus of data. Each title-oriented document comprises a title and at least one topical field. The topical field comprises a field name and field content associated with the topical field of at least one document in the corpus of data. The processor automatically creates at least one relation instance by combining a field identifier for the topical field, a title concept identifier, and a corresponding field content concept identifier. Terms in the question are analyzed to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The processor automatically compares the question topic term and the question content identifier to at least one of the at least one relation instance to identify at least one question-matching relation instance. At least one answer to the question is automatically generated by identifying the title concept identifier of each question-matching relation instance as a candidate answer to the question.
According to another embodiment herein, a computer system for scoring answers to questions in a question-answering system is disclosed. The system comprises a processor comprising an automated question answering (QA) system comprising a tangible storage device operatively connected to the processor storing a corpus of data comprising a plurality of natural language documents and a user interface operatively connected to the processor receiving a question into the automated QA system. The processor automatically constructs a plurality of title-oriented documents from the corpus of data. Each title-oriented document comprises a title and at least one topical field. The topical field comprises a field name and field content associated with the topical field of at least one document in the corpus of data. The processor automatically creates at least one relation instance by combining a field identifier for the topical field, a title concept identifier, and a corresponding field content concept identifier. The processor automatically calculates a count for each relation instance based on a number of occurrences of the title concept identifier and the field content concept identifier within a corresponding one of the at least one documents. The processor automatically analyzes terms in the question to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The processor automatically compares the at least one question topic term and the at least one question content identifier to at least one of the at least one relation instance to identify at least one question-matching relation instance. The processor automatically generates at least one answer to the question by identifying the title concept identifier of each question-matching relation instance as a candidate answer to the question. The processor generates a score for the candidate answers by adding each count within each relation instance corresponding to each candidate answer.
According to another embodiment, a question answering (QA) system is disclosed. The QA system comprises a processor comprising a named-entity extractor, a first interface connected to the processor, a second interface connected to the processor, and a non-transitory storage device operatively connected to the processor storing a corpus of data comprising a plurality of natural language documents. The first interface receives a question to be answered by the QA system. The processor automatically identifies a title and at least one topical field of at least a portion of at least one document in the corpus of data, using the named-entity extractor. The processor automatically constructs a plurality of title-oriented documents from the corpus of data. Each title-oriented document comprises the title and at least one of the at least one topical field. The topical field comprises a field name and field content associated with the topical field of at least a portion of at least one document in the corpus of data. The processor automatically constructs a structured knowledge base from the plurality of title-oriented documents. The structured knowledge base comprises at least one relation instance comprising a field identifier for the topical field, a title concept identifier, and a corresponding field content concept identifier. The processor automatically analyzes terms in the question to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The processor automatically creates a collection of candidate answers to the question. The collection of candidate answers is created from the structured knowledge base. The processor automatically outputs each candidate answer through the second interface.
According to another embodiment herein, a computer program product for answering questions in a question-answering system is disclosed. The computer program product comprises a computer readable storage medium having program code embodied therewith. The program code is readable and executable by a computer to perform a method. According to the method, a title and at least one topical field is automatically identified for at least a portion of at least one document in a grouping of documents. A field name and field content associated with the topical field is automatically identified. At least one title-oriented document is automatically created by combining the title, the field name, and the field content associated with the at least one topical field of the at least a portion of the at least one document. For each title-oriented document, at least one term in the title that corresponds to previously established categories is automatically identified to produce at least one title concept identifier. For each title-oriented document, the topical field is automatically synthesized to produce at least one field concept identifier and at least one field content concept identifier from the previously established categories. At least one relation instance is automatically created by combining, for each field concept identifier, a corresponding title concept identifier of the at least one title concept identifier and a corresponding field content concept identifier of the at least one field content concept identifier. A count for each relation instance is automatically calculated based on a number of occurrences of the title concept identifier and the field content concept identifier within a corresponding one of the at least one documents in the grouping of documents. The count is automatically included with each relation instance. A question is received. The terms in the question are automatically analyzed to identify at least one question topic term and at least one question content identifier based on previously established question term categories. The question topic term and the question content identifier are automatically compared to at least one of the at least one relation instance to identify at least one question-matching relation instance. The title concept identifier of each question-matching relation instance is automatically identified as a candidate answer to the question. Each count within each relation instance corresponding to each candidate answer is automatically added to provide an answer score for each candidate answer. Each candidate answer and a corresponding answer score are automatically output.



BRIEF DESCRIPTION OF THE DRAWINGS
The embodiments herein will be better understood from the following detailed description with reference to the drawings, which are not necessarily drawn to scale and in which:
FIG. 1 is a block diagram illustrating various aspects of embodiments herein;
FIG. 2 is a block diagram illustrating various aspects of embodiments herein;
FIG. 3 is a block diagram illustrating various aspects of embodiments herein;
FIG. 4 is a block diagram illustrating various aspects of embodiments herein;
FIG. 5 is a block diagram illustrating various aspects of embodiments herein;
FIG. 6 is a flow diagram illustrating embodiments herein;
FIG. 7 is a schematic diagram of a hardware system according to embodiments herein;
FIG. 8 is a schematic diagram of a deployment system according to embodiments herein;
FIG. 9 is a schematic diagram of an integration system according to embodiments herein;
FIG. 10 is a schematic diagram of an on demand system according to embodiments herein;
FIG. 11 is a schematic diagram of a virtual private network system according to embodiments herein; and
FIG. 12 is a schematic diagram of a virtual private network system according to embodiments herein.



DETAILED DESCRIPTION
It will be readily understood that the embodiments of the present disclosure, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations in addition to the embodiments described herein. Thus, the following detailed description of the embodiments, as represented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments. The following description is intended only by way of example, and simply illustrates certain embodiments of the invention, as claimed herein.
Referring to FIG. 1, according to one embodiment, a novel method of automatically constructing structured knowledge bases that can be used to answer questions precisely is disclosed. First, title-oriented documents (TODs) are created from a natural language corpus 111. A structured knowledge base is constructed from the TODs 121. To do this, relations are constructed between concepts in the titles of the documents and concepts in the bodies of the documents from the natural language corpus. As used herein, ‘concepts’ are formed by synthesizing the information in the title and/or text body to a representative simpler word or phrase, which is used as a concept identifier. To answer questions 131, concepts that occur in the relations constructed between the concepts in the titles of the documents and the concepts in the bodies of the documents are matched with concepts that also occur in the question. For scoring the answers to the questions 141, a count is made of the number of times the answer occurs in a concept that occurs in a constructed relation and that also has a concept that occurs in the question.
FIG. 2 shows an example for constructing a TOD. For each document in a corpus of documents about a subject matter of interest, the document 212 is converted into one or more title-oriented documents (TODs) 222. A TOD 222 includes a title and one or more topical fields associated with the title. Each topical field has a field name and field content, which includes at least a portion of the text derived from the document.
An example TOD may include:
TITLE: Rheumatoid arthritis
FIELD NAME: SYMPTOMS
FIELD CONTENT: Symptoms include inflammation and increased stiffness.
FIELD NAME: TREATMENT
FIELD CONTENT: Treatments include analgesics and NSAIDS.
The TOD title is created from the titles or headings 232 within the corpus documents. TOD fields include field names 242 and associated field content 252, and are created from headings and text in the corpus documents using a named-entity extractor. A named-entity extractor locates and classifies elements in the text into predefined categories such as the names of persons, locations, names of diseases, syndromes, conditions, diagnoses, symptoms, signs, findings, laboratory test results, quantities, organizations, expressions of times, monetary values, percentages, etc. (The preceding list is intended to include non-limiting examples of predefined categories.) While creating the TOD, variant terms used in the corpus document headings (such as “Signs and Symptoms”, “Symptoms and Signs”, and “Symptoms”) should be mapped to TOD field names according to their appropriate synonyms (such as “SYMPTOMS”, as shown at 242).
In FIG. 3, a structured knowledge base 323 is constructed from a plurality of TODs 222, 333. The structured knowledge base 323 comprises a set of relation instances 343 derived from the TODs 222, 333. A relation instance 343 may take the form (field concept identifier, unique concept identifier, unique concept identifier). Each relation instance 343 is created by combining a field concept identifier for the topical field, typically the field name, a title concept identifier, and a field content concept identifier corresponding to the title concept. The structured knowledge base 323 may also include a map from each relation instance 343 to a count 353, which is described in more detail below.
The structured knowledge base 323 may be constructed as follows:
For each TOD 222, 333 (1) perform named entity recognition on the title 232 to obtain one or more unique concept identifiers for the title, sometimes referred to herein as a title unique concept identifier (TUCI) 363; (2) for each field in the TOD 222, 333, perform named entity recognition on the field content 252 to obtain one or more unique concept identifiers for the field content, sometimes referred to herein as a field unique concept identifier (FUCI) 373. For each title unique concept identifier (TUCI) 363 and for each field unique concept identifier (FUCI) 373, increment the count 353 of the structured knowledge base relation instance (FIELD NAME,TUCI,FUCI) 343.
In some embodiments, the count can be determined based on confidence in the unique concept identifier. A “confidence” value is a real number (usually between 0.0 and 1.0) that is produced by the named entity recognizer. A confidence value of 1.0 indicates that the named entity recognizer is 100% confident that the text is referring to the unique concept identifier. A confidence value of 0.0 indicates that the named entity recognizer is 0% confident that the text is referring to the unique concept identifier. For example, when constructing the structured knowledge base, instead of incrementing the count by 1 for each occurrence of a term in the field content, the count can be incremented by [the confidence of the TUCI] multiplied by [the confidence of the FUCI]. Therefore, the “count” in the structured knowledge base may no longer be an integer count, but rather a real number. In this case, it may be referred to as a “weighted count.”
Referring to FIG. 4, the structured knowledge base 323 may be used to generate answers to questions. The terms in the question are analyzed to identify at least one question content identifier and at least one question topic term. Named entity recognition is performed on the question 414 to obtain one or more unique concept identifiers for the question 414, sometimes referred to herein as a question unique concept identifier (QUCI). In the example shown in FIG. 4, one question unique concept identifier may be related to “increased stiffness” 424 and another question unique concept identifier may be related to “inflammation” 434. Named entity recognition performed on the question 414 also obtains a question topic term, which is similar to a question unique concept identifier. In the example shown in FIG. 4, the question topic term may be related to “disease” 444.
According to embodiments herein, the question topic term 444 is compared with the structured knowledge base relation instance (FIELD NAME,TUCI,FUCI) 343 in order to search in the appropriate field. When a question unique concept identifier (QUCI) 424, 434 in the question 414 correlates with a field unique concept identifier (FUCI) 373 in the relation instance, the title unique concept identifier (TUCI) 363 may be a potential answer 454.
In some embodiments, the title unique concept identifier of each question-matching relation instance may be identified as a candidate answer to the question. However, according to embodiments herein, it is possible to apply the relation instances “in reverse”. That is, it is also possible to identify the field unique concept identifier of a question-matching relation instance as a candidate answer to the question, where the title unique concept identifier of the relation instance appears in the question.
For each (FIELD NAME,UCI1,UCI2):

    
    
        (1) If the first unique concept identifier (UCI1) is a question unique concept identifier (QUCI), generate the second unique concept identifier (UCI2) as a potential answer.
        (2) If the second unique concept identifier (UCI2) is a question unique concept identifier (QUCI), generate the first unique concept identifier (UCI1) as a potential answer.
    
    


Answers can also be made more precise by filtering answers.

    
    
        (1) If it is known what type of answer is desired, filter candidate answers by question type, and only generate answers that are of that type. For example, if it is known that the question is asking for a disease, only generate answers that are diseases.
        (2) If it is known what type of question is being asked, filter candidate answers by relation type, and only use relations instances whose field name corresponds to that type of question. For example, if it is known that the question is asking for a disease given its symptoms, only use relation instances whose FIELD NAME is “SYMPTOMS”.
    
    


FIG. 5 shows an example for how to score potential answers 454 to questions 414. Answers to questions may come from sources other than the structured knowledge base. The structured knowledge base 323 can be used to score answers that come from the structured knowledge base 323, as well as answers that come from other sources.
As described above, perform named-entity recognition on the question 414 to obtain one or more unique concept identifiers 424, 434 for the question. Given a unique concept identifier for an answer to the question, sometimes referred to herein as an answer unique concept identifier (AUCI) 515, score that answer by computing the sum of the counts 353 associated with relation instances 343 of the form (FIELD NAME,AUCI,QUCI) or (FIELD NAME,QUCI,AUCI), where QUCI is one of the unique concept identifiers for the question 434. In the example shown in FIG. 5, the QUCI for “inflammation” 434 matches the AUCI in the first line of the structured knowledge base 323 with a count 353 of twenty-three (23). The QUCI for “increased stiffness” 424 matches the AUCI in the second line of the structured knowledge base 323 with a count 353 of twelve (12). Return the sum of counts as the score of the answer. In this example, the score 525 for the answer 454 is the sum of 23+12; therefore, the score 525 is thirty-five (35).
Alternatively, compute the sum of the pointwise mutual information between the AUCI and QUCI, where QUCI is one of the unique concept identifiers for the question. In this case, return this sum of the pointwise mutual information as the score of the answer. Pointwise mutual information is a measure of association between the unique concept identifiers. That is, pointwise mutual information between unique concept identifiers UCI1 and UCI2 is defined as the logarithm base 2 of the probability that UCI1 and UCI2 co-occur divided by the probability of UCI1 times the probability of UCI2.
In embodiments where the count is a weighted count, the score is computed in a similar fashion. That is, the weighted counts are treated exactly the same way as un-weighted counts in the pointwise mutual information calculation.
Furthermore, a confidence value can be used in calculating an answer score. For example, when calculating the score for counts or for pointwise mutual information, instead of computing the sum of the counts (or pointwise mutual information, or weighted counts, or pointwise mutual information computed from weighted counts), compute the sum of the counts (or pointwise mutual information, or weighted counts, or pointwise mutual information computed from weighted counts), each of which is multiplied by the confidence associated with the matching unique concept identifier for the question, as produced by the named entity recognizer when run on the question text. A formula for using a confidence value to calculate an answer score may include:

[FinalScore of AUCI]=[Confidence of QUCI1]*[WeightedCount of (FIELD NAME,QUCI1,AUCI)]+[Confidence of QUCI2]*[WeightedCount of (FIELD NAME,QUCI2,AUCI)]+

where QUCI1 and QUCI2 appear in the question, according to the named entity recognizer and the “Confidence of QUCI1” is the named entity recognizer's confidence that QUCI1 is actually being referred to in the question.

Scores can also be made more precise by filtering the relation instances used to compute the sum as described above if it is known what type of answer is desired or what type of question is being asked.
According to embodiments herein, the system uses natural language generation to convert unstructured data into useable knowledge/model. From this knowledge, the system generates and scores answers to questions. The safer planet framework can be used to create TODs and the structured knowledge base. According to embodiments herein, the method converts documents into a structured knowledge base. The method comprises constructing relation instances between (A) named entities recognized in the title within documents and (B) named entities recognized in the text of those documents. The relation name is constructed based on what section of the document the particular named entity that has been recognized in the text (B) appears in. The number of occurrences of that named entity (B) is counted for use in scoring the answers to questions. The count is also used to compute pointwise mutual information to score answers to questions.
FIG. 6 is a flow diagram illustrating the processing flow of an exemplary method of answering questions and scoring answers using structured knowledge mined from a corpus according to embodiments herein. In item 600, a title and at least one topical field is identified for at least a portion of a document in a grouping of documents. At 607, a field name and field content associated with the topical field is identified. At least one title-oriented document is created, at 614, by combining the title, the field name, and the field content associated with the at least one topical field of the at least a portion of the document. At 621, for each title-oriented document, at least one term in the title that corresponds to previously established categories is identified to produce at least one title concept identifier. At 628, the topical field is synthesized to produce at least one field concept identifier and at least one field content concept identifier from the previously established categories. At least one relation instance is created, at 635, by combining, for each field concept identifier, a corresponding title concept identifier of the at least one title concept identifier and a corresponding field content concept identifier of the at least one field content concept identifier. At 642, a count for each relation instance is calculated based on the number of occurrences of the title concept identifier and the field content concept identifier within a corresponding one of the documents in the grouping of documents. The count is included with each relation instance, at 649. At 656, a question is received. The terms in the question are analyzed, at 663, to identify at least one question topic term. In some embodiments, one or more terms in the question may optionally be matched to previously established categories to produce a question concept identifier, at 670. At 677, the question topic term and the question content identifier are matched to at least one of the at least one relation instance to identify at least one question-matching relation instance. At 681, the title concept identifier of each question-matching relation instance is identified as a candidate answer to the question. Each count within each relation instance corresponding to each candidate answer is added, at 691, to provide an answer score for each candidate answer. At 698, each candidate answer and each corresponding answer score are output.
Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to various embodiments. It will be understood that each block of the flowchart illustrations and/or two-dimensional block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. The computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
According to a further embodiment herein, an article of manufacture is provided that includes a tangible computer readable medium having computer readable instructions embodied therein for performing the steps of the computer implemented methods, including but not limited to the method illustrated in FIG. 6. Any combination of one or more computer readable non-transitory medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The non-transitory computer storage medium stores instructions, and a processor executes the instructions to perform the methods described herein. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Any of these devices may have computer readable instructions for carrying out the steps of the methods described above with reference to FIG. 6.
The computer program instructions may be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
Furthermore, the computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
In case of implementing the embodiments herein by software and/or firmware, a program constituting the software may be installed into a computer with dedicated hardware, from a storage medium or a network, and the computer is capable of performing various functions if with various programs installed therein.
A representative hardware environment for practicing the embodiments herein is depicted in FIG. 7. This schematic drawing illustrates a hardware configuration of an information handling/computer system in accordance with the embodiments herein. The system comprises at least one processor or central processing unit (CPU) 710. The CPUs 710 are interconnected via system bus 712 to various devices such as a Random Access Memory (RAM) 714, Read-Only Memory (ROM) 716, and an Input/Output (I/O) adapter 718. The I/O adapter 718 can connect to peripheral devices, such as disk units 711 and tape drives 713, or other program storage devices that are readable by the system. The system can read the inventive instructions on the program storage devices and follow these instructions to execute the methodology of the embodiments herein.
In FIG. 7, CPUs 710 perform various processing based on a program stored in a Read Only Memory (ROM) 716 or a program loaded from a peripheral device, such as disk units 711 and tape drives 713 to a Random Access Memory (RAM) 714. In the RAM 714, required data when the CPU 710 performs the various processing or the like is also stored as necessary. The CPU 710, the ROM 716, and the RAM 714 are connected to one another via a bus 712. An Input/Output adapter 718 is also connected to the bus 712 to provide an Input/Output interface, as necessary. A removable medium, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like, is installed on the peripheral device, as necessary, so that a computer program read therefrom may be installed into the RAM 714, as necessary.
The system further includes a user interface adapter 719 that connects a keyboard 715, mouse 717, speaker 724, microphone 722, and/or other user interface devices such as a touch screen device (not shown) to the bus 712 to gather user input. Additionally, a communication adapter 720 including a network interface card such as a LAN card, a modem, or the like connects the bus 712 to a data processing network 725. The communication adapter 720 performs communication processing via a network such as the Internet. A display adapter 721 connects the bus 712 to a display device 723, which may be embodied as an output device such as a monitor (such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), or the like), printer, or transmitter, for example.
In the case where the above-described series of processing is implemented with software, the program that constitutes the software may be installed from a network such as the Internet or a storage medium such as the removable medium.
Those skilled in the art would appreciate that, the storage medium is not limited to the peripheral device having the program stored therein as illustrated in FIG. 5, which is distributed separately from the device for providing the program to the user. Examples of a removable medium include a magnetic disk (including a floppy disk), an optical disk (including a Compact Disk-Read Only Memory (CD-ROM) and a Digital Versatile Disk (DVD)), a magneto-optical disk (including a Mini-Disk (MD) (registered trademark)), and a semiconductor memory. Alternatively, the storage medium may be the ROM 716, a hard disk contained in the storage section 711, or the like, which has the program stored therein and is distributed to the user together with the device that contains them.
As will be appreciated by one skilled in the art, aspects of the systems and methods herein may be embodied as a system, method, or computer program product. Accordingly, aspects of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable non-transitory medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The non-transitory computer storage medium stores instructions, and a processor executes the instructions to perform the methods described herein. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (EPROM or Flash memory), an optical fiber, a magnetic storage device, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a “plug-and-play” memory device, like a USB flash drive, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments herein. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Deployment types include loading directly in the client, server, and proxy computers via loading a storage medium such as a CD, DVD, etc. The process software may also be automatically or semi-automatically deployed into a computer system by sending the process software to a central server or a group of central servers. The process software is then downloaded into the client computers that will execute the process software. The process software is sent directly to the client system via e-mail. The process software is then either detached to a directory or loaded into a directory by a button on the e-mail that executes a program that detaches the process software into a directory. Alternatively, the process software is sent directly to a directory on the client computer hard drive. When there are proxy servers, the process will select the proxy server code, determine on which computers to place the proxy servers' code, transmit the proxy server code, and then install the proxy server code on the proxy computer. The process software will be transmitted to the proxy server, and then stored on the proxy server.
While it is understood that the process software may be deployed by manually loading directly in the client, server, and proxy computers via loading a storage medium such as a CD, DVD, etc., the process software may also be automatically or semi-automatically deployed into a computer system by sending the process software to a central server or a group of central servers. The process software is then downloaded into the client computers that will execute the process software. Alternatively, the process software is sent directly to the client system via e-mail. The process software is then either detached to a directory or loaded into a directory by a button on the e-mail that executes a program that detaches the process software into a directory. Another alternative is to send the process software directly to a directory on the client computer hard drive. When there are proxy servers, the process will select the proxy server code, determine on which computers to place the proxy servers' code, transmit the proxy server code, and then install the proxy server code on the proxy computer. The process software will be transmitted to the proxy server, and then stored on the proxy server.
In FIG. 8, step 800 begins the deployment of the process software. The first thing is to determine if there are any programs that will reside on a server or servers when the process software is executed 801. If this is the case, then the servers that will contain the executables are identified 909. The process software for the server or servers is transferred directly to the servers' storage via FTP or some other protocol, or by copying through the use of a shared file system 910. The process software is then installed on the servers 911.
Next, a determination is made on whether the process software is to be deployed by having users access the process software on a server or servers 802. If the users are to access the process software on servers, then the server addresses that will store the process software are identified 803.
A determination is made if a proxy server is to be built 900 to store the process software. A proxy server is a server that sits between a client application, such as a Web browser, and a real server. It intercepts all requests to the real server to see if it can fulfill the requests itself. If not, it forwards the request to the real server. The two primary benefits of a proxy server are to improve performance and to filter requests. If a proxy server is required, then the proxy server is installed 901. The process software is either sent to the servers via a protocol such as FTP or it is copied directly from the source files to the server files via file sharing 902. Another embodiment would be to send a transaction to the servers that contain the process software and have the server process the transaction, then receive and copy the process software to the server's file system. Once the process software is stored at the servers, the users, via their client computers, then access the process software on the servers and copy it to their client computers file systems 903. Another embodiment is to have the servers automatically copy the process software to each client and then run the installation program for the process software at each client computer. The users execute the program that installs the process software on their client computer 912, and then exit the process 808.
In step 804, a determination is made whether the process software is to be deployed by sending the process software to users via e-mail. The set of users where the process software will be deployed are identified together with the addresses of the user client computers 805. The process software is sent via e-mail 904 to each of the users' client computers. The users receive the e-mail 905 and then detach the process software from the e-mail to a directory on their client computers 906. The users execute the program that installs the process software on their client computer 912, and then exit the process 808.
Lastly, a determination is made on whether the process software will be sent directly to user directories on their client computers 806. If so, the user directories are identified 807. The process software is transferred directly to the users' client computer directory 907. This can be done in several ways such as but not limited to sharing of the file system directories and then copying from the sender's file system to the recipient users' file system or alternatively using a transfer protocol such as File Transfer Protocol (FTP). The users access the directories on their client file systems in preparation for installing the process software 908. The users execute the program that installs the process software on their client computer 912, and then exit the process 808.
The process software is integrated into a client, server, and network environment by providing for the process software to coexist with applications, operating systems, and network operating systems software, and then installing the process software on the clients and servers in the environment where the process software will function.
The first step is to identify any software on the clients and servers including the network operating system where the process software will be deployed that are required by the process software or that work in conjunction with the process software. This includes the network operating system that is software that enhances a basic operating system by adding networking features.
Next, the software applications and version numbers will be identified and compared to the list of software applications and version numbers that have been tested to work with the process software. Those software applications that are missing or that do not match the correct version will be upgraded with the correct version numbers. Program instructions that pass parameters from the process software to the software applications will be checked to ensure the parameter lists match the parameter lists required by the process software. Conversely, parameters passed by the software applications to the process software will be checked to ensure the parameters match the parameters required by the process software. The client and server operating systems including the network operating systems will be identified and compared to the list of operating systems, version numbers, and network software that have been tested to work with the process software. Those operating systems, version numbers, and network software that do not match the list of tested operating systems and version numbers will be upgraded on the clients and servers to the required level.
After ensuring that the software, where the process software is to be deployed, is at the correct version level that has been tested to work with the process software, the integration is completed by installing the process software on the clients and servers.
In FIG. 9, step 920 begins the integration of the process software. The first thing is to determine if there are any process software programs that will execute on a server or servers at 921. If this is not the case, then integration proceeds to 927. If this is the case, then the server addresses are identified 922. The servers are checked to see if they contain software that includes the operating system (OS), applications, and network operating systems (NOS), together with their version numbers, that have been tested with the process software 923. The servers are also checked to determine if there is any missing software that is required by the process software 923.
A determination is made if the version numbers match the version numbers of OS, applications, and NOS that have been tested with the process software 924. If all of the versions match and there is no missing required software, the integration continues in 927.
If one or more of the version numbers do not match, then the unmatched versions are updated on the server or servers with the correct versions 925. Additionally, if there is missing required software, then it is updated on the server or servers 925. The server integration is completed by installing the process software 926.
Step 927, which follows either step 921, 924, or 926, determines if there are any programs of the process software that will execute on the clients. If no process software programs execute on the clients, the integration proceeds to 930 and exits. If this not the case, then the client addresses are identified 928.
The clients are checked to see if they contain software that includes the operating system (OS), applications, and network operating systems (NOS), together with their version numbers, that have been tested with the process software 929. The clients are also checked to determine if there is any missing software that is required by the process software 929.
A determination is made as to whether the version numbers match the version numbers of OS, applications, and NOS that have been tested with the process software 931. If all of the versions match and there is no missing required software, then the integration proceeds to 930 and exits.
If one or more of the version numbers do not match, then the unmatched versions are updated on the clients with the correct versions 932. In addition, if there is missing required software then it is updated on the clients 932. The client integration is completed by installing the process software on the clients 933. The integration proceeds to 930 and exits.
The process software can be stored on a shared file system accessible from one or more servers. The process software is executed via transactions that contain data and server processing requests that use CPU units on the accessed server. CPU units are units of time such as minutes, seconds, hours on the central processor of the server. Additionally, the assessed server may make requests of other servers that require CPU units. CPU units are an example that represents one measurement of use. Other measurements of use include but are not limited to network bandwidth, memory usage, storage usage, packet transfers, complete transactions etc. When multiple customers use the same process software application, their transactions are differentiated by the parameters included in the transactions that identify the unique customer and the type of service for that customer. All of the CPU units and other measurements of use that are used for the services for each customer are recorded. When the number of transactions to any one server reaches a number that begins to affect the performance of that server, other servers are accessed to increase the capacity and to share the workload. Likewise, when other measurements of use such as network bandwidth, memory usage, storage usage, etc. approach a capacity so as to affect performance, additional network bandwidth, memory usage, storage etc. are added to share the workload. The measurements of use used for each service and customer are sent to a collecting server that sums the measurements of use for each customer for each service that was processed anywhere in the network of servers that provide the shared execution of the process software. The summed measurements of use units are periodically multiplied by unit costs and the resulting total process software application service costs are alternatively sent to the customer and/or indicated on a web site accessed by the customer, which then remits payment to the service provider. In another embodiment, the service provider requests payment directly from a customer account at a banking or financial institution. In another embodiment, if the service provider is also a customer of the customer that uses the process software application, the payment owed to the service provider is reconciled to the payment owed by the service provider to minimize the transfer of payments.
The process software is shared, simultaneously serving multiple customers in a flexible, automated fashion. It is standardized, requiring little customization, and it is scalable, providing capacity on demand in a pay-as-you-go model.
The process software can be stored on a shared file system accessible from one or more servers. The process software is executed via transactions that contain data and server processing requests that use CPU units on the accessed server. CPU units are units of time such as minutes, seconds, hours on the central processor of the server. Additionally, the assessed server may make requests of other servers that require CPU units. CPU units are an example that represents one measurement of use. Other measurements of use include but are not limited to network bandwidth, memory usage, storage usage, packet transfers, complete transactions etc.
When multiple customers use the same process software application, their transactions are differentiated by the parameters included in the transactions that identify the unique customer and the type of service for that customer. All of the CPU units and other measurements of use that are used for the services for each customer are recorded. When the number of transactions to any one server reaches a number that begins to affect the performance of that server, other servers are accessed to increase the capacity and to share the workload. Likewise, when other measurements of use such as network bandwidth, memory usage, storage usage, etc. approach a capacity so as to affect performance, additional network bandwidth, memory usage, storage etc. are added to share the workload.
The measurements of use used for each service and customer are sent to a collecting server that sums the measurements of use for each customer for each service that was processed anywhere in the network of servers that provide the shared execution of the process software. The summed measurements of use units are periodically multiplied by unit costs and the resulting total process software application service costs are alternatively sent to the customer and/or indicated on a web site accessed by the customer, which then remits payment to the service provider.
In another embodiment, the service provider requests payment directly from a customer account at a banking or financial institution.
In another embodiment, if the service provider is also a customer of the customer that uses the process software application, the payment owed to the service provider is reconciled to the payment owed by the service provider to minimize the transfer of payments.
In FIG. 10, step 940 begins the On Demand process. A transaction is created that contains the unique customer identification, the requested service type, and any service parameters that further specify the type of service 941. The transaction is then sent to the main server 942. In an On Demand environment, the main server can initially be the only server, then, as capacity is consumed, other servers are added to the On Demand environment.
The server central processing unit (CPU) capacities in the On Demand environment are queried 943. The CPU requirement of the transaction is estimated, then the servers' available CPU capacity in the On Demand environment are compared to the transaction CPU requirement to see if there is sufficient CPU capacity available in any server to process the transaction 944. If there is not sufficient server CPU capacity available, then additional server CPU capacity is allocated to process the transaction 948. If there was already sufficient CPU capacity available, then the transaction is sent to a selected server 945.
Before executing the transaction, a check is made of the remaining On Demand environment to determine if the environment has sufficient available capacity for processing the transaction. This environment capacity consists of such things as, but not limited to, network bandwidth, processor memory, storage etc. 946. If there is not sufficient available capacity, then capacity will be added to the On Demand environment 947. Next, the required software to process the transaction is accessed, loaded into memory, then the transaction is executed 949.
The usage measurements are recorded 950. The usage measurements consist of the portions of those functions in the On Demand environment that are used to process the transaction. The usage of such functions as, but not limited to, network bandwidth, processor memory, storage and CPU cycles are what is recorded. The usage measurements are summed, multiplied by unit costs, and then recorded as a charge to the requesting customer 951. If the customer has requested that the On Demand costs be posted to a web site 952, then they are posted 953.
If the customer has requested that the On Demand costs be sent via e-mail to a customer address 954, then they are sent 955. If the customer has requested that the On Demand costs be paid directly from a customer account 956, then payment is received directly from the customer account 957. The last step is to exit the On Demand process 958.
The process software may be deployed, accessed and executed through the use of a virtual private network (VPN), which is any combination of technologies that can be used to secure a connection through an otherwise unsecured or untrusted network. The use of VPNs is to improve security and for reduced operational costs. The VPN makes use of a public network, usually the Internet, to connect remote sites or users together. Instead of using a dedicated, real-world connection such as leased line, the VPN uses “virtual” connections routed through the Internet from the company's private network to the remote site or employee.
The process software may be deployed, accessed, and executed through either a remote-access or a site-to-site VPN. When using the remote-access VPNs, the process software is deployed, accessed, and executed via the secure, encrypted connections between a company's private network and remote users through a third-party service provider. The enterprise service provider (ESP) sets a network access server (NAS) and provides the remote users with desktop client software for their computers. The telecommuters can then dial a toll-free number or attach directly via a cable or DSL modem to reach the NAS and use their VPN client software to access the corporate network and to access, download, and execute the process software.
When using the site-to-site VPN, the process software is deployed, accessed, and executed through the use of dedicated equipment and large-scale encryption, which are used to connect a company's multiple fixed sites over a public network, such as the Internet.
The process software is transported over the VPN via tunneling, which is the process of placing an entire packet within another packet and sending it over a network. The protocol of the outer packet is understood by the network and both points, called tunnel interfaces, where the packet enters and exits the network.
In FIGS. 11 and 12, step 960 begins the Virtual Private Network (VPN) process. A determination is made to see if a VPN for remote access is required 961. If it is not required, then proceed to 962. If it is required, then determine if the remote access VPN exists 964.
If it does exist, then proceed to 965. Otherwise, identify the third party provider that will provide the secure, encrypted connections between the company's private network and the company's remote users 976. The company's remote users are identified 977. The third party provider then sets up a network access server (NAS) 978 that allows the remote users to dial a toll-free number or attach directly via a cable or DSL modem to access, download, and install the desktop client software for the remote-access VPN 979.
After the remote access VPN has been built, or if it been previously installed, the remote users can then access the process software by dialing into the NAS or attaching directly via a cable or DSL modem into the NAS 965. This allows entry into the corporate network where the process software is accessed 966. The process software is transported to the remote users' desktop over the network via tunneling. That is, the process software is divided into packets and each packet, including the data and protocol, is placed within another packet 967. When the process software arrives at the remote users' desktop, it is removed from the packets, reconstituted, and executed on the remote users' desktop 968.
A determination is made to see if a VPN for site-to-site access is required 962. If it is not required, then proceed to exit the process 963. Otherwise, determine if the site-to-site VPN exists 969. If it does exist, then proceed to 972. Otherwise, install the dedicated equipment required to establish a site-to-site VPN 970. Then build the large-scale encryption into the VPN 971.
After the site-to-site VPN has been built, or if it had been previously established, the users access the process software via the VPN 972. The process software is transported to the site users over the network via tunneling 973. That is, the process software is divided into packets and each packet, including the data and protocol, is placed within another packet 974. When the process software arrives at the remote users' desktop, it is removed from the packets, reconstituted, and executed on the site users' desktop 975. Proceed to exit the process 963.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of this disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The descriptions of the various embodiments herein have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

## Claims

1. A computer system for scoring answers to questions in a question-answering system, comprising:
a processor comprising an automated question answering (QA) system comprising:
a tangible storage device operatively connected to said processor, said tangible storage device storing a corpus of data comprising natural language documents; and
a user interface operatively connected to said processor, said user interface receiving a question into said automated QA system,

said processor constructing title-oriented documents from said corpus of data, each title-oriented document comprising a title and a topical field, said topical field comprising a field name and field content associated with said topical field of a document in said corpus of data,
said processor creating a relation instance by combining a field identifier for said topical field, a title concept identifier, and a corresponding field content concept identifier,
said processor calculating a count for each said relation instance based on a number of occurrences of said title concept identifier and said field content concept identifier within a corresponding document in said corpus of data,
said processor analyzing terms in said question, said analyzing identifying a question content identifier based on previously established question term categories,
said processor comparing said question content identifier to said relation instance, said comparing identifying a question-matching relation instance,
said processor generating an answer to said question by identifying said title concept identifier of each said question-matching relation instance as a candidate answer to said question, and
said processor generating a score for said candidate answer by adding each said count within each said relation instance corresponding to said candidate answer.

2. The computer system of claim 1, said count for each said relation instance further comprising pointwise mutual information.

3. The computer system of claim 1, said processor including said count with each said relation instance.

4. The computer system of claim 1, further comprising a named-entity extractor to locate and classify elements in said natural language document into predefined categories for said title and said field name, and
said processor constructing said title-oriented documents from said corpus of data further comprising:
for each said title-oriented document, identifying a term in said title that corresponds to said predefined categories to produce a title concept identifier; and
for each said title-oriented document, synthesizing said topical field to produce a field concept identifier and a field content concept identifier from said predefined categories.

5. The computer system of claim 1, said processor further
identifying a title and a topical field of a portion of a document in said corpus of data; and
identifying field content associated with said topical field.

6. A question answering (QA) system comprising:
a processor comprising a named-entity extractor;
a first interface operatively connected to said processor;
a second interface operatively connected to said processor; and
a non-transitory storage device operatively connected to said processor, said non-transitory storage device storing a corpus of data comprising natural language documents,
said first interface receiving a question to be answered by said QA system,
said processor identifying a title and a topical field of a portion of a document in said corpus of data, using said named-entity extractor,
said processor constructing title-oriented documents from said corpus of data, each said title-oriented document comprising said title and a topical field, said topical field comprising a field name and field content associated with said topical field of a document in said corpus of data,
said processor constructing a structured knowledge base from said title-oriented documents, said structured knowledge base comprising a relation instance comprising a field identifier for said topical field, a title concept identifier, and a corresponding field content concept identifier,
said processor calculating a count for each said relation instance based on a number of occurrences of said title concept identifier and said field content concept identifier within a corresponding document in said corpus of data comprising natural language documents,
said processor analyzing terms in said question to identify a question content identifier based on previously established question term categories,
said processor creating a collection of candidate answers to said question, said collection of candidate answers being created from said structured knowledge base,
said processor generating a score for said candidate answers by adding each said count within each said relation instance corresponding to said candidate answers, and
said processor outputting each said candidate answer through said second interface.

7. The question answering system of claim 6, said processor constructing said title-oriented documents from said corpus of data further comprising:
for each said title-oriented document, identifying a term in said title that corresponds to previously established categories, using said QA system, said identifying producing a title concept identifier; and
for each said title-oriented document, synthesizing said topical field, said synthesizing producing a field concept identifier and a field content concept identifier from said previously established categories.

8. The question answering system of claim 6, said processor analyzing terms in said question further comprising:
identifying a type of question; and
filtering said candidate answers according to said type of question.

9. The question answering system of claim 6, said processor analyzing terms in said question further comprising:
identifying a type of relation based on said question; and
filtering said relation instances according to said type of relation.

10. A computer program product for answering questions in a question-answering system, said computer program product comprising a non-transitory computer readable storage medium having program code embodied therewith, said program code being readable and executable by a computer to perform a method, comprising:
identifying a title and a topical field of a portion of a document in a grouping of documents;
identifying a field name and field content associated with said topical field;
creating a title-oriented document by combining, said title, said field name, and said field content associated with said a topical field of said portion of said document;
for each said title-oriented document, identifying a term in said title that corresponds to previously established categories to produce a title concept identifier;
for each said title-oriented document, synthesizing said topical field to produce a field concept identifier and a field content concept identifier from said previously established categories;
creating a relation instance by combining, for each said field concept identifier, a corresponding title concept identifier of said title concept identifier and a corresponding field content concept identifier of said field content concept identifier;
calculating a count for each said relation instance based on a number of occurrences of said title concept identifier and said field content concept identifier within a corresponding document in said grouping of documents;
including said count with each said relation instance;
receiving a question into said computer;
analyzing terms in said question to identify a question content identifier based on previously established question term categories;
comparing said question content identifier to said relation instance to identify a question-matching relation instance;
identifying said title concept identifier of each said question-matching relation instance as a candidate answer to said question;
adding each said count within each said relation instance corresponding to each said candidate answer to provide an answer score for each said candidate answer; and
outputting each said candidate answer and each corresponding said answer score from said computer.

11. The computer program product according to claim 10, said grouping of documents comprising natural language documents.

12. The computer program product according to claim 10, said identifying said term in said title that corresponds to previously established categories further comprising using a named-entity extractor to locate and classify elements in said term into predefined categories.

13. The computer program product according to claim 10, said analyzing terms in said question further comprising:
identifying a type of question; and
filtering said candidate answers according to said type of question.

14. The computer program product according to claim 10, said analyzing terms in said question further comprising:
identifying a type of relation based on said question; and
filtering said relation instances according to said type of relation.

15. The computer program product according to claim 10, said count for each said relation instance further comprising pointwise mutual information.