Benjamin Aw
Add updated pkl file v3
6fa4bc9
raw
history blame contribute delete
No virus
39.4 kB
{
"paper_id": "M91-1011",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T03:15:37.245585Z"
},
"title": "LANGUAGE SYSTEMS, INC . MUC-3 TEST RESULTS AND ANALYSIS 1",
"authors": [
{
"first": "Christine",
"middle": [
"A"
],
"last": "Montgomery",
"suffix": "",
"affiliation": {},
"email": ""
},
{
"first": "Bonnie",
"middle": [
"Glover"
],
"last": "Stalls",
"suffix": "",
"affiliation": {},
"email": ""
},
{
"first": "Robert",
"middle": [
"S"
],
"last": "Belvin",
"suffix": "",
"affiliation": {},
"email": ""
},
{
"first": "Robert",
"middle": [
"E"
],
"last": "Stumberger",
"suffix": "",
"affiliation": {},
"email": ""
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "",
"pdf_parse": {
"paper_id": "M91-1011",
"_pdf_hash": "",
"abstract": [],
"body_text": [
{
"text": "Language Systems, Inc .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "6269 Variel Avenue, Suite F Woodland Hills, CA 91367 lsiO01%lsi-la .uucp@ism .isc.com 1-818-703-503 4 RESULTS Table 1 summarizes LSI ' s scores for Phase II of MUC-3 . In evaluating these scores, which place LSI about two/thirds of the way down in a results-ranked list of MUC-3 participants, it should be noted that our MUC-3 system reflects a major redevelopment of the key components of the DBG message understanding system, whic h is currently in process . Specifically, innovative development of a parser based on government-binding principle s is under way, 2 with associated revisions of the lexicon, functional parse (recovery of the predicate/argumen t functions representing the underlying semantic structure of the sentence), and DBG template 3 generation and frame hierarchy components (the areas indicated by the heavy lines in the system flow chart shown in Figure 1 ) . This innovative development is described more fully in the system summary paper. For the purposes of thi s site report, it is obvious that the \"under construction\" status of the DBG system had considerable impact upo n our ability to achieve a respectable score. Had we chosen instead to go with the fairly robust previous version o f the DBG system (described in [2] and [3] , recently evaluated for Rome Laboratory by KSC, Inc .), our MUC-3 scores would certainly have been substantially better, because all components of the DBG system would have been fully functional (see the discussion on functionality of the DBG version currently under developmen t below) .",
"cite_spans": [
{
"start": 1249,
"end": 1252,
"text": "[2]",
"ref_id": "BIBREF13"
},
{
"start": 1257,
"end": 1260,
"text": "[3]",
"ref_id": "BIBREF14"
}
],
"ref_spans": [
{
"start": 110,
"end": 117,
"text": "Table 1",
"ref_id": "TABREF1"
},
{
"start": 872,
"end": 880,
"text": "Figure 1",
"ref_id": null
}
],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "However, we felt strongly that the time had come to replace our chart parser with weighted rules by a mor e powerful and generic model that would provide a better foundation for current work, including automated translation and the integration of speech processing with the DBG system, as well as for the complex MUC-3 messages . Once the decision was made to embark upon this major re-development of the key DBG system components, it would have been unproductive to carry out the MUC-3 development in parallel on the older versio n of the DBG system (as well as infeasible given LSI's available resources for MUC-3).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "For the reasons described above, the bulk of our development effort was concentrated on the parser (approximately 60% of the total MUC-3 development effort) and the lexicon (approximately 30% of the total effort) , Message 96 since our earlier system of categories and features had to be substantially revised and enhanced to provide all the subcategorization and selection information required by the GB parser. The remaining 10% of the effort was devoted to the higher level components for semantic and pragmatic interpretation at the sentence and messag e level (i.e., the functional parse, (DBG) template generation and frames component, and back-end applicatio n component for extracting data for filling MUC-3 templates .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "ALLOCATION OF EFFOR T",
"sec_num": null
},
{
"text": "Since December, approximately 10,000 new lines of commented Prolog code have been written, and are in the process of being debugged. The lexicon developed for MUC-3 comprised almost 10,000 entries includin g inflected forms . In comparison, the unclassified lexicon for the air activities messages recently completed fo r Rome Laboratory [3] included only about 1500 entries, and the most recent lexicon for the Army maneuver dialogs is estimated at about 3,000 entries . The MUC-3 frames component includes 3485 frames and 257 classe s of items. However, much of this information was not exploited properly since, as mentioned above, very littl e of the MUC-3 development effort could be devoted to the higher level DBG components which utilize fram e and slot information.",
"cite_spans": [
{
"start": 338,
"end": 341,
"text": "[3]",
"ref_id": "BIBREF14"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "ALLOCATION OF EFFOR T",
"sec_num": null
},
{
"text": "In LSI's case, these included all of the items on the NOSC list of possible limiting factors, i .e ., time, people , cpu cycles, and knowledge (interpreted as limitations on system use of available knowledge), as discusse d below .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "LIMITING FACTORS",
"sec_num": null
},
{
"text": "There were not enough person hours available to LSI under the given resource limitations to carry out th e full effort required for MUC-3 in the time allotted, as well as to perform on other in-house contracts . Although particular sentence types represented in the MUC-3 texts were no more complex than in previous projects suc h as the air activities work carried out for Rome Laboratory, there was a great deal more variety in the sentenc e types in the MUC-3 texts, and the time and resources available were substantially less than the 18 months an d $225K dedicated to the Rome effort .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Time/Peopl e",
"sec_num": null
},
{
"text": "The main problem here is that we were essentially developing and debugging a substantial number of line s of new code, requiring detailed tracing facilities to identify and fix bugs . In addition, a key component for MUC3 texts is LUX (Lexical Unexpected Inputs) and its associated module WAM (Word Acquisition Module ) which deal with items not present in the DBG lexicon, either because they are misspellings of existing entries , or because they are new words . LUX in particular consumes a lot of cpu cycles, but is absolutely critical fo r processing of texts containing many words which are unknown to the DBG lexicon .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Cpu Cycle s",
"sec_num": null
},
{
"text": "In order to complete Test 2 in some finite time frame, it was therefore necessary to limit the input to th e DBG message understanding system by utilizing some fairly draconian measures . Discourse analysis of the development corpus revealed that detecting the transitions from descriptions of one event to another in the text s was too complicated to attempt within the limited resources, so all messages labeled as relevant were arbitraril y truncated to 10 sentences . Since the intent was to exclude all but event reports, which typically describe th e event(s) of interest within the 10 sentence segment, it did not appear that much information loss would resul t from this measure. No attempt was made to determine the number of MUC-3 templates represented in the truncated text that began at the 11th sentence of all messages in the critical event directory . (For further discussion , see LSI's section in the paper on discourse processing within the MUC-3 context included in this proceedings .)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Cpu Cycle s",
"sec_num": null
},
{
"text": "The selection of relevant messages, which was performed using Logicon's Message Dissemination Syste m (LMDS), 4 was thus executed to exclude all potentially windy messages such as reports of political speeches , interviews, and clandestine radio broadcasts of political propaganda, as well as military attack events and dru g traffic related events not involving terrorist acts . Critical event and irrelevant message criteria were defined i n terms of LMDS profiles and used to filter the test message set into the groups shown in Table 2 . The LMDS filtering was performed as a pre-processing run which took less than a minute for the total test set of 100 messages . In Table 2 , false positives (in terms of the MUC-3 test key) in the critical event directory and false negatives in the \"nohit\" d irectory are indicated by Xs. Table 3 contains numbers of the messages which were partially processed, but produced no template outpu t because processing hung up in the parser. Per the instructions for running the test procedure, processing was restarted with the next relevant message following these parser failures .",
"cite_spans": [],
"ref_spans": [
{
"start": 532,
"end": 539,
"text": "Table 2",
"ref_id": "TABREF2"
},
{
"start": 673,
"end": 680,
"text": "Table 2",
"ref_id": "TABREF2"
},
{
"start": 831,
"end": 838,
"text": "Table 3",
"ref_id": "TABREF3"
}
],
"eq_spans": [],
"section": "Cpu Cycle s",
"sec_num": null
},
{
"text": "The DBG system was fairly well primed with knowledge, as can be seen from the size of the lexicon and th e frames data bases cited previously. However, because the the GB parser was not completely functional (in fact, was still undergoing extensive debugging, as mentioned above), many attachments were not being made, resulting in a large number of partial trees which could not labeled with their thematic roles (i .e ., agent, patient, etc .) . The consequences of these attachment failures propagated throughout the remainder of the processing components, resulting in predicate/argument functions unlabeled, unindexed, or missing in the functional parse, s o that the DBG templates were extremely sparse, as were the MUC-3 application templates. Figures 2 and 3 show partial output for Test 2 Message 100, which illustrates this point. Essentially because of the limited functionality of the GB parser at this stage of development, a great deal of the knowledge represented in the frame hierarchy and associated rules, as well as knowledge represented in the rules for filling the MUC-3 templates, wa s never exploited by the system .",
"cite_spans": [],
"ref_spans": [
{
"start": 751,
"end": 766,
"text": "Figures 2 and 3",
"ref_id": "FIGREF0"
}
],
"eq_spans": [],
"section": "Knowledge Availability vs. System Functionalit y",
"sec_num": null
},
{
"text": "It goes without saying that the development corpus was extremely useful in lexical, syntactic, semantic, an d discourse analysis for system development . We also found the treebank analysis of MUC-3 messages very useful for identifying the multitude of possible variations on a single syntactic theme . Due to the partially functional status of the evolving GB parser, we were unable to fully exploit the 1300 messages in testing for this phase of MUC-3, but were limited to a few messages that we used for regression testing. The MUC-3 corpus is a very valuable archive that we intend to utilize more fully in the next few months, as our parser stabilizes an d we can take advantage of the variety of texts represented in the MUC-3 collection .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "TRAININ G",
"sec_num": null
},
{
"text": "Most of the components of the DBG system have been at least revised and extended, and in most cases , completely replaced, as part of our evolutionary design philosophy (see the system summary paper for a discussion) .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MODULE MOST OVERDUE FOR REWRITIN G",
"sec_num": null
},
{
"text": "As noted previously, however, one of the oldest modules in the system is the Lexical Unexpected Inputs (LUX) module, and its associated Word Acquisition Module (WAM) . These modules attempt to determin e whether an unexpected lexical input (i .e ., one which is not present in the lexicon) is erroneous (e .g., a misspelling of an entry actually present in the lexicon), or entirely new . In the first case, LUX goes through an elaborate procedure to determine whether a spelling error exists, which is corrected if a reasonable hypothesis fo r an association with a word in the lexicon can be found (e .g ., in test 1, the form \"kidapped\" was corrected to \"kidnapped\") . If no correction can be made, the form is determined to be new, which requires WAM to provid e a temporary grammatical category assignment so that the sentence containing the new word can be parsed .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MODULE MOST OVERDUE FOR REWRITIN G",
"sec_num": null
},
{
"text": "As noted previously, our lexicon included approximately 10,000 words ; however, the vocabulary in th e MUC-3 development corpus is estimated at 20,000 words (see Hirschman paper in this proceedings) . Clearly , the LUX/WAM components were of inestimable value to us in processing the test sets ; it would have bee n impossible to run without them . On the other hand, because of the many new words encountered in the MUC-3 texts, LUX and WAM had to be used many times on every message, and because these procedures are nonoptimized at present, the amount of time devoted to autonomous LUX/WAM processing was substantial .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "MODULE MOST OVERDUE FOR REWRITIN G",
"sec_num": null
},
{
"text": "Another module that should be rewritten for higher efficiency is LXI, which handles lexical lookup and morphological processing; however, LUX/WAM are first on the list . [1 .1 ] agent : colombian army of national liberatio n agent_org :",
"cite_spans": [
{
"start": 170,
"end": 177,
"text": "[1 .1 ]",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "MODULE MOST OVERDUE FOR REWRITIN G",
"sec_num": null
},
{
"text": "army of national liberation Action kidnap [1 .2 ] Action abduct [1 .3 ] agent ",
"cite_spans": [
{
"start": 42,
"end": 49,
"text": "[1 .2 ]",
"ref_id": null
},
{
"start": 64,
"end": 71,
"text": "[1 .3 ]",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "MODULE MOST OVERDUE FOR REWRITIN G",
"sec_num": null
},
{
"text": ". The work reported in this paper was supported in part by the Defense Advanced Research Projects Agency, InformationSystems and Technology Office, under Contract No . MDA903-89-C-0041 (Subcontract MC 1350) 2. Unlike chart parsers, which are based on a well-understood model that has been in existence for almost 30 years, very few attempts hav e been made at implementing GB parsers (see[1]), and LSI's implementation approach differs from these in several important respects .3. It is important to note that the term \"template \" in the DBG system is a label for the generic message level semantic and pragmati c representational units, not an application oriented structure like the MUC-3 templates . It is the glass box output or interna l representational output, as opposed to the MUC-3 templates, which are black box outputs mapped to the external representation require d by a given application : currently, extraction of specific data elements for describing terrorist incidents in 9 Latin American countries .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": ". LMDS does shallow text analysis based on boolean combinations of key words/phrases with proximity and other criteria, which operat e as search logic specifications within particular user-defined zones of messages (e .g ., mediasource zone, with typical contents such as \"Radio Venceremos\", \"Television Peruana\", etc .).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
}
],
"back_matter": [
{
"text": "The DBG system developed for the MUC-3 application is completely reusable on other applications, with th e exception of the rules for deriving the output MUC-3 templates from the DBG templates, which is the backen d especially tailored for the MUC-3 application . Other than that, there are a few features such as an attribute i n the frame system entitled \"critical event\", which would not be useful in another application, but there are ver y few of these (another such feature does not even come to mind at this point) .",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "REUSABILITY",
"sec_num": null
},
{
"text": "Since we have performed several MUC-like tasks (i.e., data extraction) as described in the system summary , as well as evaluations, the main lesson learned was not to postpone further the acquisition of an on-line dictionary such as Longmans or the OED . In any case, had we made such an acquisition for MUC-3, time an d resources would have been insufficient to integrate it with the other system components and exploit it within th e MUC-3 context.With respect to evaluation, the evaluations performed by LSI on the systems described in [2] and [3] bot h included competitive testing in the template-filling task against a human user or simulated user of the type o f information in the given domain . This type of evaluation is perhaps more difficult in the MUC case, but, base d on our experience, is extremely significant for users, because it is more believable to them than a series of finel y tuned scores .",
"cite_spans": [
{
"start": 539,
"end": 542,
"text": "[2]",
"ref_id": "BIBREF13"
},
{
"start": 547,
"end": 550,
"text": "[3]",
"ref_id": "BIBREF14"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "LESSONS LEARNED",
"sec_num": null
}
],
"bib_entries": {
"BIBREF1": {
"ref_id": "b1",
"title": "prep)",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "'Pmaxl'+(1 .3) : Pmax (Pbar (Pbar (P ( [in) :prep) , Nmax(Nbar(N((colombia] :noun)))) , Nmax(Nbar(N([colombia] :noun))))) .",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Ibar(I))",
"authors": [
{
"first": "",
"middle": [],
"last": "Imax",
"suffix": ""
}
],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Imax(Ibar(I)) .",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "Nmax (Nbar (N ([release) :noun) , Genmax (Genbar (Gen ((of) :of)",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "' Vmax3' + (1 .5) : Vmax(Vbar(V((confirmed) :past) , Dmax(Dbar(D([the] :det) , Nmax (Nbar (N ([release) :noun) , Genmax (Genbar (Gen ((of) :of) , Amax (Abar(A([red] :adj) , Nmax (Nbar (NC (globo] :noun) , Nmax(Nbar(N( [journalist) :noun) , Nmax(Nbar(N([carlos) :noun_name) , Nmax (Nbar (N ( [marcelo] :noun) ) )",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "Vicemax(Vicebar(Aux ((was) :aux) , Vmax(Vbar(Vbar(V",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Vicemaxl'+(1 .0) : Vicemax(Vicebar(Aux ((was) :aux) , Vmax(Vbar(Vbar(V([kidnapped] :pastpart) , Argmax(Argbar( ' Arg' :'*empty*'))) ,",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "prep) , Amax",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Pmax(Pbar(P([by] :prep) , Amax (Abar(A([colombian] :adj) , Nmax(Nbar(N(['army of national liberation'] :noun) , Nmax(Nbar (N ( (guerrillas] :plural) ) )",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "1 ' ) = embass y ' DESCRIPTION' (' 1 . 1' ) = ' INDEX' (' 1 .2' ) 'COUNTRY' ( . 1 .2' ) = colombi a 'MAINPRED' (' 1 .2' ) = ' INDEX' (' 1 .3' ) 'MAINPRED' ( . 1 .3' ) = 'INDEX'('1 .4' ) 'PRED' (' 1 .4' ) = hav e 'MAINPRED' ( . 1 .4' ) = ' INDEX' (' 1 .5' ) 'PRED'('1 .5') = confirm 'DETERMINER' ('1 .5') = th e ' MATERIAL_ACT ' ('1 .5') = 'release of red globo journalist carlos marcelo",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "SENTENCE-LEVEL SEMANTIC INTERPRETATIO N functional-parse-1 : 'MAINPRED'('1 .0') = ' INDEX' (' 1 . 1' ) 'DETERMINER' ( . 1 .1' ) = th e 'ARG'('1 .1') = brazilia n 'FOREIGN _ GOVT_ FACILITY' ( . 1 . 1 ' ) = embass y ' DESCRIPTION' (' 1 . 1' ) = ' INDEX' (' 1 .2' ) 'COUNTRY' ( . 1 .2' ) = colombi a 'MAINPRED' (' 1 .2' ) = ' INDEX' (' 1 .3' ) 'MAINPRED' ( . 1 .3' ) = 'INDEX'('1 .4' ) 'PRED' (' 1 .4' ) = hav e 'MAINPRED' ( . 1 .4' ) = ' INDEX' (' 1 .5' ) 'PRED'('1 .5') = confirm 'DETERMINER' ('1 .5') = th e ' MATERIAL_ACT ' ('1 .5') = 'release of red globo journalist carlos marcelo ' 'MAINPRED' (' 1 .5' ) = ' INDEX' (' 1 . 6 , ) 'MAINPRED' (' 1 . 6' ) = wh o ' MAINPRED' (' 1 . 6' ) _ ' INDE X ' (' 1 . 7 , ) ' EVENT' (' 1 .7' ) = kidna p 'AGENT' ('1 .7') 'colombian army of national liberation ' 'ORG'('1 .7') 'army of national liberation ' ' AGENT' (' 1 .7' ) = guerrilla s 'MAINPRED' (' 1 . 7' ) = 'INDEX'('1 .8' )",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "MESSAGE I D 1. TEMPLATE I D 2. DATE OF INCIDEN T 3. TYPE OF INCIDEN T 4. CATEGORY OF INCIDENT 5. PERPETRATOR : ID OF INDIV(S ) 6. PERPETRATOR : ID OF ORG(S ) 7. PERPETRATOR : CONFIDENC E 8. PHYSICAL TARGET : ID(S )",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "MESSAGE I D 1. TEMPLATE I D 2. DATE OF INCIDEN T 3. TYPE OF INCIDEN T 4. CATEGORY OF INCIDENT 5. PERPETRATOR : ID OF INDIV(S ) 6. PERPETRATOR : ID OF ORG(S ) 7. PERPETRATOR : CONFIDENC E 8. PHYSICAL TARGET : ID(S )",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "EFFECT ON HUMAN TARGET(S )",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "EFFECT ON HUMAN TARGET(S )",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "MESSAGE I D 1. TEMPLATE I D 2. DATE OF INCIDEN T 3. TYPE OF INCIDEN T 4. CATEGORY OF INCIDEN T 5. PERPETRATOR : ID OF INDIV(S ) 6. PERPETRATOR : ID OF ORG(S ) 7. PERPETRATOR : CONFIDENC E 8. PHYSICAL TARGET : ID(S )",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "MESSAGE I D 1. TEMPLATE I D 2. DATE OF INCIDEN T 3. TYPE OF INCIDEN T 4. CATEGORY OF INCIDEN T 5. PERPETRATOR : ID OF INDIV(S ) 6. PERPETRATOR : ID OF ORG(S ) 7. PERPETRATOR : CONFIDENC E 8. PHYSICAL TARGET : ID(S )",
"links": null
},
"BIBREF10": {
"ref_id": "b10",
"title": "EFFECT ON HUMAN TARGET(S)",
"authors": [],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "EFFECT ON HUMAN TARGET(S)",
"links": null
},
"BIBREF12": {
"ref_id": "b12",
"title": "Principle-Based Parsing",
"authors": [
{
"first": "R",
"middle": [
"C"
],
"last": "Berwick",
"suffix": ""
}
],
"year": 1987,
"venue": "",
"volume": "972",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Berwick, R . C ., Principle-Based Parsing, AI TR No . 972, June, 1987 .",
"links": null
},
"BIBREF13": {
"ref_id": "b13",
"title": "The DBG Message Understanding System",
"authors": [
{
"first": "C",
"middle": [
"A"
],
"last": "Montgomery",
"suffix": ""
},
{
"first": "J",
"middle": [],
"last": "Burge",
"suffix": ""
},
{
"first": "H",
"middle": [],
"last": "Holmback",
"suffix": ""
},
{
"first": "J",
"middle": [
"L"
],
"last": "Kuhns",
"suffix": ""
},
{
"first": "B",
"middle": [
"G"
],
"last": "Stalls",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Stumberger",
"suffix": ""
},
{
"first": "R",
"middle": [
"L"
],
"last": "Russel",
"suffix": ""
}
],
"year": 1989,
"venue": "Proceedings of the Annual At Systems in Governmen t Conference",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Montgomery, C . A., Burge, J ., Holmback, H., Kuhns, J . L ., Stalls, B . G ., Stumberger, R ., Russel, R . L . , The DBG Message Understanding System, in Proceedings of the Annual At Systems in Governmen t Conference (1989), IEEE Computer Society Press, 1989 .",
"links": null
},
"BIBREF14": {
"ref_id": "b14",
"title": "Long Range Air (LRA) Data Base Generator (DBG)",
"authors": [
{
"first": "B",
"middle": [],
"last": "Stalls",
"suffix": ""
},
{
"first": "R",
"middle": [],
"last": "Stumberger",
"suffix": ""
},
{
"first": "C",
"middle": [
"A"
],
"last": "Montgomery",
"suffix": ""
}
],
"year": 1990,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Stalls, B ., R . Stumberger, and C . A . Montgomery (1990) . Long Range Air (LRA) Data Base Generator (DBG). RADC-TR-89-366.",
"links": null
}
},
"ref_entries": {
"FIGREF0": {
"uris": null,
"type_str": "figure",
"text": "Partial Syntactic and Semantic Parse Output for Message 100 (TST2 )",
"num": null
},
"FIGREF1": {
"uris": null,
"type_str": "figure",
"text": "*************************************************************************DBG-Templates and MUC-3-Templates for Message 100 (TST2 )",
"num": null
},
"TABREF0": {
"text": "",
"type_str": "table",
"content": "<table><tr><td>SLOT</td><td/><td>REC</td><td>PRE</td><td colspan=\"2\">OVG</td><td>FAL</td></tr><tr><td colspan=\"2\">MATCHED ONLY MATCHED/MISSING</td><td>32 16</td><td>48 48</td><td/><td>22 22</td><td>U . A</td></tr><tr><td colspan=\"2\">ALL TEMPLATES</td><td>16</td><td>33</td><td/><td>46</td><td>s</td><td>E .</td></tr><tr><td colspan=\"2\">SET FILLS ONLY</td><td>15</td><td>45</td><td/><td>32</td><td>0</td><td>I : -.</td></tr><tr><td/><td>iN :</td><td/><td/><td/><td/></tr><tr><td/><td>ullili !</td><td/><td/><td/><td/></tr><tr><td/><td colspan=\"6\">,111~!tt~ll ll~~tl .z~!l1~,1111i, i</td></tr><tr><td/><td>;t</td><td colspan=\"5\">!IIIi ii~tlii!1l1~i1liil1 l t t t t</td></tr><tr><td>l</td><td colspan=\"6\">_ ' l .g1= -!~=--11 ;-;11 i t 11 l 4 11'1~1Fl~t iltt11 !ri e a t ;11111 ' !il lt, ti . . -a t ;li ---' ' 011 1111;1</td></tr><tr><td/><td/><td/><td/><td/><td/><td>.</td></tr><tr><td/><td/><td>uT :</td><td>( l</td><td>+1</td><td colspan=\"2\">1l !s1? ~: 1</td><td>E</td></tr><tr><td/><td/><td>h</td><td/><td/><td colspan=\"2\">`-</td></tr><tr><td/><td/><td/><td/><td colspan=\"2\">I hi:</td></tr><tr><td/><td/><td/><td colspan=\"3\">1 II 11; 1 li i il i 1 llt' t I ! iili ,t : ; i 1 ;</td></tr><tr><td/><td/><td/><td/><td>li ii1li</td><td>llh!i1</td><td>I</td></tr><tr><td/><td/><td/><td/><td/><td/><td>II</td></tr><tr><td/><td colspan=\"5\">Figure 1 : Functional Flow of the System</td></tr></table>",
"num": null,
"html": null
},
"TABREF1": {
"text": "",
"type_str": "table",
"content": "<table><tr><td colspan=\"2\">SUMMARY OF SCORES</td></tr><tr><td>FALSE POSITIVE</td><td>FALSE NEGATIVE</td></tr><tr><td/><td>Message 01 Message 4 6</td></tr><tr><td/><td>Message 08 Message 54</td></tr><tr><td/><td>Message 16 Message 56</td></tr><tr><td/><td>Message 18 Message 5 7</td></tr><tr><td/><td>Message 19 Message 6 8</td></tr><tr><td/><td>Message 24 Message 74</td></tr><tr><td/><td>Message 28 Message 7 8</td></tr><tr><td/><td>Message 31 Message 80</td></tr><tr><td/><td>Message 32 Message 90</td></tr><tr><td/><td>Message 36 Message 9 3</td></tr><tr><td/><td>Message 39 Message 95</td></tr><tr><td/><td>Message 4 2</td></tr></table>",
"num": null,
"html": null
},
"TABREF2": {
"text": "INCORRECTLY CLASSII hD MESSAGES (RELEVANT VS . IRRELEVANT)",
"type_str": "table",
"content": "<table><tr><td>Message 0 7</td></tr><tr><td>Message 10</td></tr><tr><td>Message 1 1</td></tr><tr><td>Message 1 6</td></tr><tr><td>Message 23</td></tr><tr><td>Message 3 0</td></tr><tr><td>Message 67</td></tr><tr><td>Message 77</td></tr><tr><td>Message 86</td></tr><tr><td>Message 9 1</td></tr><tr><td>Message 9 9</td></tr></table>",
"num": null,
"html": null
},
"TABREF3": {
"text": "",
"type_str": "table",
"content": "<table><tr><td>UNPROCESSED MESSAGE S</td></tr></table>",
"num": null,
"html": null
}
}
}
}