{ "paper_id": "X96-1017", "header": { "generated_with": "S2ORC 1.0.0", "date_generated": "2023-01-19T15:05:28.200272Z" }, "title": "Cable Abstracting and INdexing S_ystem (CANIS) Prototype", "authors": [ { "first": "Ira", "middle": [], "last": "Sider", "suffix": "", "affiliation": { "laboratory": "", "institution": "Lockheed Martin Corporation", "location": { "postBox": "P.O. Box 8048", "postCode": "19101", "settlement": "Philadelphia", "region": "PA" } }, "email": "sider@mds.lmco.com" }, { "first": "Jeffrey", "middle": [], "last": "Baker", "suffix": "", "affiliation": { "laboratory": "", "institution": "Lockheed Martin Corporation", "location": { "postBox": "P.O. Box 8048", "postCode": "19101", "settlement": "Philadelphia", "region": "PA" } }, "email": "jbaker@mds.lmco.com" }, { "first": "Deborah", "middle": [], "last": "Brady", "suffix": "", "affiliation": { "laboratory": "", "institution": "Lockheed Martin Corporation", "location": { "postBox": "P.O. Box 8048", "postCode": "19101", "settlement": "Philadelphia", "region": "PA" } }, "email": "brady_d@mds.lmco.com" }, { "first": "Lynne", "middle": [], "last": "Higbie", "suffix": "", "affiliation": { "laboratory": "", "institution": "Lockheed Martin Corporation", "location": { "postBox": "P.O. Box 8048", "postCode": "19101", "settlement": "Philadelphia", "region": "PA" } }, "email": "higbie@mds.lmco.com" }, { "first": "Tom", "middle": [], "last": "Howard", "suffix": "", "affiliation": { "laboratory": "", "institution": "Lockheed Martin Corporation", "location": { "postBox": "P.O. Box 8048", "postCode": "19101", "settlement": "Philadelphia", "region": "PA" } }, "email": "howard@mds.lmco.com" } ], "year": "", "venue": null, "identifiers": {}, "abstract": "", "pdf_parse": { "paper_id": "X96-1017", "_pdf_hash": "", "abstract": [], "body_text": [ { "text": "The CANIS customer receives cables from sites world-wide, indexes the entities mentioned in these cables and stores that information for access by analysts at a later date. The CANIS customer indexes large quantifies of information mostly manually, and wishes to reduce the human rescmrces applied to this task.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "Incoming cables are processed, information is extracted and stored in Corporate Databases. Cables with useful data are abstracted and indexed.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "Abstracting captures information about the cable itself: its document number, source, date, etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "Indexing captures information about the entities described in the cable: their names, dates of birth, locations, etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "The result of the abstracting and indexing process is a set of index records about the entities that were described in a cable.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "When a cable has been abstracted and indexed, its index record(s) are placed in a queue so that they will be stored. When file maintenance is performed (periodically overnight), the index records are stored in the Corporate Database.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "The abstracting and indexing process is a time consuming and laborious task. Analysts must read every cable and extract the infcmnation that should be placed in the new index records or update existing records. Although the abstracting portion of the task has been automated, it is only a small part of the ab-stracting and indexing process. The majority of the effort is the indexing part of the process. At present, there is little or no automation support for the indexing part of the process.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "The CANIS prototype is intended to assist the CANIS customer with the cable indexing task. CANIS automatically extracts entity information, builds and updates index records from cables, and presents it for review. CANIS' analysts can 1) approve the system generated index records, 2) add more information to the system generated index records, or 3) ignore the system generated index records and create their own. CANIS also extracts and stores relationship information (such as family relations, employment, and affiliations). This information is not currently identified or stored during the manual indexing task.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "CANIS is compatible with both the input and output systems currently being used by the CANIS customer. CANIS runs on the customer-specified hardware and software plaffozms. However, the prototype CANIS system is a stand-alone system. ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "", "sec_num": null }, { "text": "The Comm Process CSCI retrieves the Cable Data from the Cable Delivery System Server at a constant given rate via a software timer. The Comm Process CSCI creates a Document from the Cable Data and passes the Document to the Document Manager Process CSCI which stores this information in a Document Collection. The Comm Process CSCI sends the Collection Identifier and Document Identifier to the Extraction Process CSCI. The Comm Process CSCI also transfers the Cable Delivery System Header information to the SQL Database as it relates to the Document in the CoLlection.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Comm Process CSCI", "sec_num": "3.1." }, { "text": "The Extraction Process CSCI processes each Collection Identifier and Document Identifier passed to it. The Extraction Process CSCI passes the Collection and Document Identifiers to the Document Manager CSCI which retrieves and returns the document text. The Extraction Process CSCI extracts biographical entities found within the document using Lockheed Martin's NLToolset. The Extraction Process CSCI passes the extracted entities to the Document Manager Process CSCI, which stores them as Annotations on the Document. The Extraction Process CSCI sends the Collection Identifier and Document Identifier to the Analyst Data Setup Process CSCI.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Extraction Process CSCI", "sec_num": "3.2." }, { "text": "Upon initialization, the Extraction Process CSCI spawns the NLToolset Server Object, which ties all the NLToolset's data resources together into a single object, and loads into it the NLToolset System Specification File. This fde contains a set of entries that identify the resources that should be loaded, the debug flags that should be set, the organization of the resources, and the sequence of operations that the NLToolset should perform. The primary resources that are loaded are: ", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Extraction Process CSCI", "sec_num": "3.2." }, { "text": "\u2022 Lexicon \u2022 Ontology \u2022 Gazetteer \u2022 Abbreviation \u2022 Special", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Extraction Process CSCI", "sec_num": "3.2." }, { "text": "Tokenizatiou creates a buffer of tokens from the Document's text. All words, punctuation, numbers, etc. in a Document are processed into tokens. The information captured for each token is: physical string, token symbol, token type. symbol id, part of speech, string case type, and character start and end positions.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Processing.", "sec_num": null }, { "text": "Segmentation breaks the Document's token buffer into paragraphs and sentences based on multiple newlines, tabs, periods, etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Processing.", "sec_num": null }, { "text": "Reduction performs multiple passes through the Document buffer looking for sequences of tokens that can be simplified into a single identifiable unit. These passes are used to identify specific pieces of information needed for Extraction. \u2022 Family \u2022 Employment \u2022 Affiliations Post Processing creates Annotations for all the data items and entities. These Annotations are then attached to the Document and stored in the Document Manager Process CSCI. Appendix A contains the Annotation Design Specification for these entities.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Processing.", "sec_num": null }, { "text": "The Analyst Data Setup Process CSCI processes each Collection Identifier and Document Identifier pair passed to it. It then passes the Collection and Document Identifiers to the Document Manager Process CSCI which retrieves and returns the Document and its Annotations. The Annotations for this document are placed into relational records in the CANIS Server (SQL Server). Names, Organizations and Associations entities found within the extracted annotations are validated against existing entities. If the entity exists, then the new information is linked to the existing entities. If the entity does not exist, new relational records are created for that entity.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "The Analyst Data Setup Process CSCI collects and builds relations for each of the major entities (Personnel, Organizations, and Associations) within the Annotations for the Document in the Collection. It validates and connects different types of locations, numbers and biographic information. For each entity, the process validates against existing index relations. If the entity exists, all information is processed as an update to the existing records. If the entity does not exist, the record is added to the relational database as a currently known Index record. Biographical entities are connected to the named entity through the ODBC SQLServer API. Biographical entity type connections are: gender, country of birth, date of birth, etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "Additionally, the process operates on address earlties and number entities and connects these to the named entities. It validates the address and number information against existing data relations. If the address or number exists, then all information is processed as a reference to the existing records. Otherwise, anew record containing the information is added to the relations and connected to the named entity. The types of addresses captured are: location, residence, etc. The types of numbers captured are: phone, license, etc.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "The Analyst Data Setup Process CSCI links named entities together through relation links in the SQL data-base. The process will link the following entity information: Family (persons to family), Employment (persons to organizations), and Affiliation (persons to associations).", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "The Analyst Data Setup Process CSCI validates File Numbers against existing relations and connects them to named entities. The types of Filing and Document Reference data connected are: System Folder Objects and Document IDs.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "Finally, the Analyst Data Setup Process CSCI adds the Document to an analyst working queue for processing by an analyst through the Analyst Interface Process CSCI.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "The Analyst Data Setup Process bridges the gap hetween the information that was extracted from each Document and the information currently stored in the customer's database.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Data Setup Process CSCI", "sec_num": "3.3." }, { "text": "The Analyst Interface Process CSCI processes User Commands passed to it. These Commands allow an analyst to access and manipulate all the information stored in the CANIS prototype. When a Document is selected for display by an analyst, the Analyst Interface Process CSCI passes the Collection Identifier and Document Identifier for the Document to the Document Manager Process CSCI which retrieves and returns the Document and its relational records.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "The Analyst Interface Process CSCI displays a summary list of the named entities associated with the selected Document. An analyst may select a given entity from the list and review the enfity's detailed information, delete the entity from the list, or lookup a new entity found in the body of the Document. For each of the details available about a name, (ie. biographies, relationships, id numbers, locations, phone numbers etc.) the analyst reviews, modifies the informatiou if necessary, and checks off the information. Some of the data, such as gender, citizenship, or relationship types, for example, have alternative choices available on a pulldown menu to minimize key strokes necessary to make changes.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "The Analyst Interface Process CSCI allows an analyst to review and modify all information (Index records, addressees, subject line, and Fding locations) about a Document. It will display a Document's text body and allow the analyst to travel through the processing of the information about that Document. The following functions are available to an analyst: Document Details Review, CANIS Prototype Process Logs Review, Name Lookup and Processing, and System Filing. Document Details Review displays the classification, addressees, and subject line associated with the current Document. The analyst may review and modify any of this information.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "CANIS Prototype Process Logs Review displays the logs generated by each of the CANIS System Processes in read-only mode. The information captured by these logs includes: document identifiers for documents processed, error messages, system generated messages (ie. debug).", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "The Document Name Lookup and Processing allows the review and modification of named entities (Personnel, Company, and Associations) of the selected Document. The options available to an analyst here are, a) Name Lookup, b) Index, Review Data records for this entity, c) Create Links between Entity names and reviewed records: and d) Add and Modify Information associated with the entity (ie. gender, citizenship, locations, phone numbers, etc.)", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "Extraction errors found by the analyst during their processing of a document are appended to a log within the SQL database for review by an engineer for Extraction CSCI package adjustments.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Analyst Interface Process CSCI", "sec_num": "3.4." }, { "text": "The Document Manager Process CSCI is a set of library routines which provide a standard interface between the CANIS Prototype and the persistent storage of documents. The Document Manager conforms to the concepts and specifications of the TIPSTER Phase II Architecture Design Document (version 1.15). The Library routines of the Document Manager Process provides all CSCI's of the CANIS Prototype with a standard interface (APD for accessing docmnents, and communicaring annotation information about those documents.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Document Manager Process CSCI", "sec_num": "3.5." }, { "text": "The Document Manager Process CSCI is implemented on top of a relational database with access to the database facilitated through ODBC library calls. The Document Manager Process CSCI uses Microsoft's ODBC library. Microsoft Access and Microsoft SQLServer. Other applications using Lockheed Marfin's Document Manager are being built on top of Sybase and Oracle.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Document Manager Process CSCI", "sec_num": "3.5." }, { "text": "The NLToolset is a framework of tools, techniques and resources for building text processing applications. The NLToolset is portable, extensible, robust, genetic and language independent. The NLToolset combines artificial intelligence (AD methods, especially NL processing, knowledge-based systems and information retrieval techniques, with simpler methods, such as finite state machines, lexical analysis and word-based text search to provide broad functionality without sacrificing robustness and speed.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "NLTOOLSET", "sec_num": "4." }, { "text": "The NLToolset currently runs on SUN Microsystem's UN/X-based platforms and PCs (using Microsoft Windows NT). The NLToolset is coded in C++ and uses the COOL Object Library. The CANIS application is PC based and using the Microsoft Visual C++ compiler and Visual Basic on the PC.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "NLTOOLSET", "sec_num": "4." }, { "text": "We are currently in the testing phase and developing the evaluation criteria in conjunction with the government These phases are scheduled to complete, July 1996.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "TESTING AND EVALUATION", "sec_num": "5." }, { "text": "Our Test Plan involves subsystem testing of each of the Comms Process CSCI, Extraction Process CSCI, Analyst Data Setup Process CSCI, and the Analyst Interface Process CSCI. We are also performing System Level Integration Testing to validate the data passing through each process within the CANIS application.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "TESTING AND EVALUATION", "sec_num": "5." }, { "text": "Evaluation will be performed by analysts at their site using real data. We are currently working with the customer to determine evaluation criteria.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "TESTING AND EVALUATION", "sec_num": "5." }, { "text": "The CANIS prototype will show the customer a new way of doing business. Analysts will see their tasks change from manually reading and creating index records to verifying and updating automatically generated index records. Their daily process will involve more analysis than data entry and they will be able to process a larger number of documents in a single day.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "6, CONCLUSIONS", "sec_num": null } ], "back_matter": [], "bib_entries": { "BIBREF2": { "ref_id": "b2", "title": "TIPSTER Phase II Document Manager Snecifiv cation (vl. 15)", "authors": [], "year": null, "venue": "", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "TIPSTER Phase II Document Manager Snecifi- v cation (vl. 15)", "links": null } }, "ref_entries": { "FIGREF0": { "uris": null, "text": "CANIS External Interface Design The CANIS prototype, as illustrated in Figure 1.0, will take as input, Cable Text, Cable Header, and Cable Delivery System Server Fields. CANIS performs all processing and stores the results internally. Users can visualiTe the processed data via the User Display.", "type_str": "figure", "num": null }, "FIGREF1": { "uris": null, "text": "0 -CANIS Top Level Process Overview 0 shows the top level design of the CANIS prototype. Cables are delivered to CANIS via the Cable Delivery System Server. This server acts as a communication driven pipe to the CANIS Prototype.", "type_str": "figure", "num": null }, "TABREF3": { "type_str": "table", "content": "
\u2022 File Numbers
\u2022 Cable Numbers
The following associations will be extracted by the
CANIS Prototype from the Cables:
\u2022 Person Names (All Types)
\u2022Company/Organization Names
\u2022 Locations
\u2022 Dates
\u2022 Phone Numbers
\u2022 License Numbers
\u2022Identification Numbers (exam-
ple: Social Security)
\u2022 Gender
\u2022Country of Birth
\u2022 Date of Birth
\u2022 Occupation
\u2022Subject Line
", "html": null, "num": null, "text": "Extraction and Reference Resolution are the NLToolset functions that glue all individual pieces together to create the entities. The information automatically extracted by CANIS from the Cables includes data of the following types:" } } } }