<?xml version="1.0" standalone="yes"?>
<Paper uid="M98-1011">
  <Title>NYU: Description of the Proteus#2FPET System as Used for MUC-7 ST</Title>
  <Section position="2" start_page="0" end_page="0" type="intro">
    <SectionTitle>
INTRODUCTION
</SectionTitle>
    <Paragraph position="0"> Through thehistory of the MUC's, adapting InformationExtraction #28IE#29 systems toanew class of events has continued tobeatime-consumingand expensivetask. Since MUC-6, the Information Extraction e#0Bort at NYU has focused on the problem of portabilityand customization, especially atthe scenario level. To begin to address this problem, wehave builtasetoftools, which allowtheusertoadapt the system tonew scenarios rapidly by providing examples of eventsintext, and examples of associated database entries to be created. The system automatically uses this information to create general patterns, appropriate for text analysis. The present system operates on twotiers: #0F Proteus #7B core extraction engine, an enhanced version of theone employed at MUC-6, #5B3#5D #0F PET #7B GUI frontend, through whichtheuserinteracts with Proteus, #28as described recently in #5B5,6#5D#29 It is our hope thatthe example-based approach will facilitatethe customization of IE engines; we are particularly interested, #28as are other sites#29, in providingthe non-technical user #7B such as a domain analyst, unfamiliar with system internals, #7B withthe capabilityto perform IE e#0Bectively in a #0Cxed domain.</Paragraph>
    <Paragraph position="1"> In this paper we discuss the system's performance on the MUC-7 Scenario Templatetask #28ST#29. Thetopics covered in the following sections are: the Proteus core extraction engine; the example-based PET interface to Proteus; a discussion of howthese were used to accommodatethe MUC-7 Space Launch scenario task.</Paragraph>
    <Paragraph position="2"> We conclude withtheevaluation of the system's performance and observations regarding possible areas of improvement.</Paragraph>
  </Section>
class="xml-element"></Paper>