<?xml version="1.0" standalone="yes"?>
<Paper uid="C88-1077">
  <Title>INTERPRETATION OF NOUN PHRASES IN INTENSIONAL CONTEXTS</Title>
  <Section position="7" start_page="382" end_page="382" type="concl">
    <SectionTitle>
5. CONCLUSIONS
</SectionTitle>
    <Paragraph position="0"> We have described a semantic network formalism that is able to cope wifll the problems arising when NP's occur as objects of verbs inducing an intensional context. The mp,esentation preserves in an easily a,-cessible format all information needed to distinguish among the lU)ssible readings, and the construction of tile net can be carried on ({eterministically (see the discussion of paragraph 3 and note that di:~ambiguating among different readings only consists in adding arcs to existing subnets), llowever, some problems still have to be solved concerning the final representation obtained by the process of mew, ing the meaning of the sentence under analysis with the discourse hi~tory. Actually, the &amp;quot;assertional&amp;quot; cmnponent of hybrid lortnalisms (see, for-instance, \[Brachman et al. 83\]) does rtot lend itself to handling intensional objects created duting.~he analysis. As stated above, we have structured the assel,ional component providing facilities for copying the subnetworks containing the description of intensional entities into it. On tire other hand, some work still has to be made in {,rdcr to provide such a component with a clear semantics.</Paragraph>
    <Paragraph position="1"> We believe that basic insights can be found in the SNePS system \[Maida &amp; Shapiro 821, \[Shapiro &amp; Rapaport 86\], where the proposed organization meet,s more clearly the requirements set forth by the existence o1' intensional olrjects.</Paragraph>
    <Paragraph position="2"> The version of the interpreter described in this paper is implemented in FRANZ LISP and runs on a SUN workstation under the UNIX operating system. The maintenance of tim discourse history and the merging process is currently under implementation.</Paragraph>
  </Section>
class="xml-element"></Paper>