<?xml version="1.0" standalone="yes"?>
<Paper uid="H01-1009">
  <Title>Automatic Pattern Acquisition for Japanese Information Extraction</Title>
  <Section position="13" start_page="2" end_page="2" type="concl">
    <SectionTitle>
6. FUTURE WORK
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="2" end_page="2" type="sub_section">
      <SectionTitle>
Information Extraction
</SectionTitle>
      <Paragraph position="0"> To apply the acquired patterns to an information extraction task, further steps are required besides those mentioned above. Since the patterns are a set of the binary relationships of a predicate and another element, it is necessary to merge the matched elements into a whole event structure.</Paragraph>
      <Paragraph position="1">  We have not yet attempted any (lexical) generalization of pattern candidates. The patterns can be expanded by using a thesaurus and/or introducing a new (lexical) class suitable for a particular domain. For example, the class of expressions of flight number clearly helps the performance on the airplane accident scenario. Especially, the generalized patterns will help improve recall.</Paragraph>
    </Section>
    <Section position="2" start_page="2" end_page="2" type="sub_section">
      <SectionTitle>
Robust Pattern Extraction
</SectionTitle>
      <Paragraph position="0"> As is discussed in the previous section, the performance of our system relies on each component. If the scenario is difficult for the IR task, for example, the whole result is affected. The investigation of a more conservative approach would be necessary.</Paragraph>
      <Paragraph position="1"> Translingualism The presented results show that our procedure of automatic pattern acquisition is promising. The procedure is quite general and addresses problems which are not specific to Japanese. With an appropriate morphological analyzer, a parser that produces a dependency tree and an NE-tagger, our procedure should be applicable to almost any language.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>