<?xml version="1.0" standalone="yes"?>
<Paper uid="M92-1006">
  <Title>GE ADJUNCT TEST REPORT : OBJECT-ORIENTED DESIGN AND SCORING FOR MUC- 4</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
INTRODUCTION
</SectionTitle>
    <Paragraph position="0"> 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 .</Paragraph>
    <Paragraph position="1"> 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 .</Paragraph>
    <Paragraph position="2"> 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 .</Paragraph>
    <Paragraph position="3"> 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 &amp;quot;pseudo-object&amp;quot; . 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 (&amp;quot;MARY&amp;quot;) 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 .</Paragraph>
  </Section>
class="xml-element"></Paper>