<?xml version="1.0" standalone="yes"?>
<Paper uid="P98-1030">
  <Title>Terminology Finite-State Preprocessing for Computational LFG</Title>
  <Section position="7" start_page="199" end_page="199" type="concl">
    <SectionTitle>
5 Conclusion and possible extensions
</SectionTitle>
    <Paragraph position="0"> The experiment presented in this paper shows the advantage of treating terms as single tokens in the preprocessing stage of a parser. It is an example of interaction between low level finite-state tools and higher level grammars. Its shows the benefit from such' a cooperation for the treatment of terminology and its implication on the syntactic parse results. One can imagine other interactions, for example, to use a &amp;quot;guesser ''3 transducer which can easily process unknown words, and give them plausible mophological analyses according to rules about productive endings.</Paragraph>
    <Paragraph position="1"> There are ambiguity sources other than terminology, but this method of ambiguity reduction is compatible with others, and improves the perspicuity of the results. It has been shown to be valuable for other syntactic phenomena like time expressions, where local regular rules can compute the morphological variation of such expressions. In general, lexicalization of (fixed) multiword expressions, like complex preposition or adverbial phrases, compounds , dates, numerals, etc., is valuable for parsing because it avoids creation of &amp;quot;had hoc&amp;quot; and unproductive syntactic rules like ADV ..~ N Coord N to parse corps et rime {body and soul), and unusual lexicon entries like fur to get au fur et d mesure (as one goes along). Ambiguity reduction and better relevance of results are direct consequences of such a treatment.</Paragraph>
    <Paragraph position="2"> This experiment, which has been conducted on a small corpus containing few terms, will be extended with an automatic extraction and integration process on larger scale corpora and other languages.</Paragraph>
    <Paragraph position="3"> ZAlready used in tagging applications</Paragraph>
  </Section>
class="xml-element"></Paper>