| { | |
| "paper_id": "M92-1006", | |
| "header": { | |
| "generated_with": "S2ORC 1.0.0", | |
| "date_generated": "2023-01-19T03:13:20.417260Z" | |
| }, | |
| "title": "GE ADJUNCT TEST REPORT : OBJECT-ORIENTED DESIGN AND SCORING FOR MUC-4", | |
| "authors": [ | |
| { | |
| "first": "George", | |
| "middle": [], | |
| "last": "Krupka", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "Artificial Intelligence Laborator y GE Research and Development Schenectady", | |
| "institution": "", | |
| "location": { | |
| "postCode": "12301", | |
| "region": "NY", | |
| "country": "US A" | |
| } | |
| }, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Lisa", | |
| "middle": [], | |
| "last": "Ra", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "Artificial Intelligence Laborator y GE Research and Development Schenectady", | |
| "institution": "", | |
| "location": { | |
| "postCode": "12301", | |
| "region": "NY", | |
| "country": "US A" | |
| } | |
| }, | |
| "email": "" | |
| } | |
| ], | |
| "year": "", | |
| "venue": null, | |
| "identifiers": {}, | |
| "abstract": "This paper reports on the results of the adjunct test performed by GE for the MUC-4 evaluatio n of text processing systems. In this test, we evaluated the effect of an object-oriented templat e design and associated matching conditions on the scores. The results indicate that the curren t MUC-.{ \"flat \" templade design with cross-references closely approximates a true object-oriente d design. However the object-oriented design allows for additional performance data to be calculated , facilitating diagnosis .", | |
| "pdf_parse": { | |
| "paper_id": "M92-1006", | |
| "_pdf_hash": "", | |
| "abstract": [ | |
| { | |
| "text": "This paper reports on the results of the adjunct test performed by GE for the MUC-4 evaluatio n of text processing systems. In this test, we evaluated the effect of an object-oriented templat e design and associated matching conditions on the scores. The results indicate that the curren t MUC-.{ \"flat \" templade design with cross-references closely approximates a true object-oriente d design. However the object-oriented design allows for additional performance data to be calculated , facilitating diagnosis .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Abstract", | |
| "sec_num": null | |
| } | |
| ], | |
| "body_text": [ | |
| { | |
| "text": "In this adjunct test, we investigate the issues and effect of transforming the MUC-4 template design automatically into an object-oriented design, with associated object-level matching conditions affecting th e overall score .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "An object is simply a collection of slots that all refer to one item originating in the text . This collection of slots is logically connected due to their implicit reference to one particular filler . In addition, objects may be nested so that one object contains another object, or may be recursive, with one object pointing t o another and back again . Finally, there may be multiple instances of any given object .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "In MUC-4 is is possible to isolate three distinct levels of objects . The first level contains a STORY object . Attached to a STORY object are INCIDENT objects, each of which contains participant objects ; TARGET , INSTRUMENT and PERPETRATOR. The Figure 1 illustrates an object-oriented template design .", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 247, | |
| "end": 255, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF0" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "The MUC template design has been moving from a flat structure to a more object-oriented structur e with cross-references tying together multiple slots into what has been termed a \"pseudo-object\" . Slots tie d together with cross-references are pseudo-objects and not true objects because the cross-references are no t enforced . For example, consider the following scenario depicted in Figure 2 . Although the human target (\"MARY\") is wrong, the system is allowed partial credit for the other slots, even though they are clearl y cross-referenced to different, and equal incorrect, fills .", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 386, | |
| "end": 394, | |
| "text": "Figure 2", | |
| "ref_id": "FIGREF1" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "INTRODUCTION", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "There are a variety of reasons why an object-oriented design is desirable . First, an object-oriented desig n is conceptually easier to understand . Instead of a flat listing of all slots of a template, slots pertaining to a single fill are grouped together . Cross-references are no longer needed, as indentation indicates the grouping , so the visual design is cleaner .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "MOTIVATIO N", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Asthetics aside, there are additional performance data that can be obtained when groups of slots ar e connected as objects . Systems can be scored on how well a given object aligns, in a way analogous t o template matching alignment scores (template ID score) . Moreover, it is possible to construct an object total that does not consider whether any given object appears in a matching template or not . For exampl e in our system, we found that data such as a human target was correctly extracted by the program with all it s associated fields, but was put in the wrong template . This resulted in missing and spurious points for all th e fields in the object, although it could be argued that all that was incorrect was the association of the objec t with an incorrect incident . Finally, with objected-oriented totals, it is very easy to isolate performanc e problems down to the object-level . With a flat design, less-than-perfect templates must be examined t o determine where the problems occurred . With object matching totals, it is possible to immediately isolat e object-level errors which facilitates the error diagnosis process . The rest of this paper maps out the processes used to transform the flat MUC-4 template design to a n object-oriented design . We then overview the scoring experiments we performed to test the effect of variou s configurations . Finally, we present detailed analyses of the effect of object-oriented design and scoring o n the data from MUC-4 systems performance .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "MOTIVATIO N", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "HUM TGT : ID : \"MARY\" HUM TGT : ID : \"JOSE \" HUM TGT : DESC : \"WIFE\" : \"MARY\" HUM TGT : DESC : \"WIFE\" : \"GEORGE \" HUM TGT : TYPE CIVILIAN : \"MARY\" HUM TGT : TYPE CIVILIAN : \" PEDRO \" HUM TGT : EFFECT : DEATH : \"MARY\" HUM TGT : EFFECT : DEATH : \" RAUL \" The first step in performing this test was to automatically transform the existing template design to the object-oriented design illustrated in Figure 1 . This process was aided by the existing cross-references, but was complicated by a variety of special cases we encountered. These special cases fell into two general categories; system glitches, and problems with the MUC-4 template format. The first three problems described below are system glitches; the last three are issues in the design of the templates.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 397, | |
| "end": 405, | |
| "text": "Figure 1", | |
| "ref_id": "FIGREF0" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "KEY RESPONS E", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "1. Inconsistent cross-references: We encountered inconsistent cross-reference strings. For example, ' 'PEOPLE' J may have been present as a human target description, but a slot intended to cross-reference to it may have read \"TWO PEOPLE j .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "KEY RESPONS E", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "2. Violation of T e m p l a t e Filling Rules: Some sites cross-referenced the perpetrator confidence to a null value, or to the PERP ID slot for example.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "KEY RESPONS E", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "We encountered fills such as NO INJURY NO DEATH INJURY DEATH.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "4. Inconsistent treatments: The treatment of repeated fills, as could be required in sentences such as \"KILLED 3 PEOPLE AND INJURED 2 a was handled in different ways, with PEOPLE repeated as a fill, or with two EFFECTS cross-referenced to one fill.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": ". When an EFFECT has a blank value, its scoping is ambiguous. When we attempt 5. Ambiguity of ' ' -' '.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "to group targets into objects, we cannot decide which object this effect belongs to.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "6. Ambiguity of Optional Fills: It is impossible with the current template design to determine when an optional fill of an optional object was meant, as opposed to a required fill of an optional object.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "For the system problems, we manually intervened and allowed the conversion process to proceed. However one sites' responses were too unusual too allow us to transform the output without a great deal of manual interaction. For the template design problems, we came up with adequate methods of working around the problems.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Multiple Set Fills:", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "After all (execept one) of the sites' answers were transformed into the object-oriented design, a modified version of the MUC-4 scoring program was run in a variety of configurations to test the effect of enforcing object-level matching. This program used the merged history file, and took 10 seconds to score an average run. It took one person-week to convert all the sites' answer templates to the object oriented design, and create a new version of the scoring program to use this design.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "OBJECT-ORIENTED SCORING", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "We experimented with a variety of conditions for aligning templates and objects. These were:", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "OBJECT-ORIENTED SCORING", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "1. Only incident type match. This was closer to the MUC-2 scoring conditions.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "OBJECT-ORIENTED SCORING", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "2. Must match on incident type, plus either a match on ID or type for target or ID or ORG for perpetrator. This duplicated the MUC-4 scoring, in that either a match on target or perpetrator would cause the incident to align.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "OBJECT-ORIENTED SCORING", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "3. Must match on incident type plus a match on the string ID slot of a target. With this condition, we only aligned templates if the targets aligned according to a stricter matching condition. This matching condition required at least a partial match on the target string. Note that virtually no templates have no targets.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "OBJECT-ORIENTED SCORING", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Free-floating object match. For this design, we computed the score if objects were allowed to match each other without considering if they happen to belong to an aligning template object. That is, if a system mistyped an ATTACK as an ARSON but correctly extracted any human or physical targets, credit would be given for these objects. ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "4.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "One of the advantages of object-oriented scoring is that it is possible to obtain object alignment totals, an d object matching totals . Figure 6 illustrates this type of data for our system on MUC-3 (a description of ou r system and a summary of our performance can be found in this volume) . The META SLOT table contains a measurement of how well our system aligned objects . The OBJECT-TOT table is useful to compare the totals for object matches when objects that appear in different templates are not scored, with the FF-OBJECT TOT table which presents the \"free-floating\" objec t totals, allowing for matches between unaligned objects that appear in incorrect templates to contribute t o recall and precision . The PSEUDO TOT table gives the pseudo-object numbers presented at the bottom of ou r score report for comparison .", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 137, | |
| "end": 145, | |
| "text": "Figure 6", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "DISCUSSIO N", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "One benefit of object-oriented design is that there can be only one representation of each unique object . This representation can be pointed to by a variety of slots . This allows for credit to be assigned once for eac h matching object, with separate credit assigned for attaching the object correctly in whichever relationship s it participates in .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "FUTURE WORK", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Primarly to ensure that the total number of points in this adjunct test was comparable to the the tota l number of points in the official scores, we did not make objects unique . However we believe that assignin g credit for extracting information from an object once would increase the accuracy of the evaluation .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "FUTURE WORK", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "This paper has reported on an adjunct test performed in connection with MUC-4 to investigate the utilit y and issues involved in object-oriented template design and scoring . We have shown that an object-oriente d design, even when modified to enforce partial string matching as the criterion for object alignment, doe s not significantly alter the MUC-4 scores . Object-oriented design is a more intuitive method of representin g information that is related . Moreover, objects can be aligned, allowing for object-level scoring . This increase s the usefulness of an automated scoring program to perform selective diagnosis for performance evaluation . Also, object-oriented alignment allows for the scoring of objects that match even when they are placed i n an incorrect template . This yields a more accurate evaluation of performance than scoring all the slots of a misplaced object as missing and spurious .", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "SUMMARY", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "The papers in this section were prepared by each of the sites that complete d the MUC-4 evaluation . The papers are intended to provide the reader with som e context for interpreting the test results, which are presented more fully i n appendices G and H of the proceedings . The sites were asked to comment on the following aspects of their MUC-4 experience : *", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PART II: TEST RESULTS AND ANALYSI S (SITE REPORTS)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Explanation of test settings (precision/recall/overgeneration ) and how these settings were chosen * Where bulk of effort was spent, and how much time was spen t overall on MUC-4 * What the limiting factor was (time, people, CPU cycles , knowledge, . . . ) * How the training of the system was don e What proportion of the training data was used (and how ) Whether/Why/How the system improved over time, an d how much of the training was automate d ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "PART II: TEST RESULTS AND ANALYSI S (SITE REPORTS)", | |
| "sec_num": null | |
| } | |
| ], | |
| "back_matter": [], | |
| "bib_entries": {}, | |
| "ref_entries": { | |
| "FIGREF0": { | |
| "uris": null, | |
| "num": null, | |
| "type_str": "figure", | |
| "text": "Object-oriented MUC-4 Template Desig n" | |
| }, | |
| "FIGREF1": { | |
| "uris": null, | |
| "num": null, | |
| "type_str": "figure", | |
| "text": "Example of Unenforced Cross-reference s TRANSFORMATION TO 0-0 DESIGN" | |
| } | |
| } | |
| } | |
| } |