<?xml version="1.0" standalone="yes"?>
<Paper uid="C86-1081">
  <Title>A LOGICAL FORMALISM FOR THE REPRESENTATION OF DETERMINERS f</Title>
  <Section position="5" start_page="346" end_page="346" type="concl">
    <SectionTitle>
CONCLUDING REMARKS
</SectionTitle>
    <Paragraph position="0"> Interpretation of de~terminers and quantifiers is usually over-simplified in many natural language interfaces. We think the for~ melism discussed in this paper constitutes a significant step in representing the meaning of the sentence at a more abstract level than many interfaces do; at the same time we can directly exploit the features of this representation to build the actual update cor~nand or query.</Paragraph>
    <Paragraph position="1"> Other approaches use a direct translation of the sentence from its surface form (or from a purely syntactic tree) into a representation language which is actually a KB ~ement or a DB query language. The formalism discussed in this pages does not make any assumption on the language used for actually accessing the KB (and for this reason the formalism does represent the meaning of a sentence in a natural or at least 'neutral' way \[Hobbs 1985, Schubert &amp; Pelletier 1982\]).</Paragraph>
    <Paragraph position="2"> On the other hand, the formalism is not too far from the way the domain kncwledge is (or could be) represented inside a KB or DB, so that it is easy to develop translation rules stating ~nat operations on the KB or DB should be done.</Paragraph>
    <Paragraph position="3"> The constraints on the available space prevented us ~ discussing the problem of using the context to disambiguate among the different meanings of a given determiner (e.g. specific vs.</Paragraph>
    <Paragraph position="4"> unspecific &amp;quot;a&amp;quot;). Some efforts were made and the results are encouraging, though in irony cases it is only very high-level information (e.g. ~utual knowledge and beliefs) can provide the basis for selecting the right interpretation.</Paragraph>
  </Section>
class="xml-element"></Paper>