File Information

File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/intro/79/p79-1013_intro.xml

Size: 4,246 bytes

Last Modified: 2025-10-06 14:04:15

<?xml version="1.0" standalone="yes"?>
<Paper uid="P79-1013">
  <Title>The Use of Ooject-Specl flc Knowledge in Natural Language Processing</Title>
  <Section position="3" start_page="53" end_page="54" type="intro">
    <SectionTitle>
3. I~U~ROORAM
</SectionTitle>
    <Paragraph position="0"> I will now describe the processing ot two sentences very similar to those discussed earlier. The computer program (OPUS) which performs the Following analyses was developed usin~ a con:eptual analyzer written by Larry Eirnbaum \[1\]. OPUS was then extended to include a capacity For setting up and Firing &amp;quot;demons&amp;quot; or .triggers&amp;quot; as they are called In K~L \[3\]. The Functioning of these demons will be Illustrated below.</Paragraph>
    <Section position="1" start_page="53" end_page="54" type="sub_section">
      <SectionTitle>
3.1 THE INITIAL ANALXSIS
</SectionTitle>
      <Paragraph position="0"> In the processing of the sentence &amp;quot;Jo~n opened the bottle so he could pour the wine,&amp;quot; the phrase &amp;quot;John opened the bottle,&amp;quot; is analyzed to produce the Followin~ representation:</Paragraph>
      <Paragraph position="2"> Here 3ELF refers to the object bein~ described (the bottle) and ?--- indicates an unfilled slot. eJohne here stands For the internal memory representation For a person wlth the name John. Memory tokens rot John and the bottle are constructed by a general demon which is trtg&amp;ered during conceptual analysis whenever a PP (the internal representation For an object) is Introduced.</Paragraph>
      <Paragraph position="3"> OF descriptions are attached to each object token.</Paragraph>
      <Paragraph position="4"> This dtagrem represents the assertion that John did something which caused the bottle to assume a state where its CONNECTOR description applied. The CONNECTOR description indicates that something can be removed from the bottle, put into the bottle, or Its contents can be smelled, looked at, or generally examined by some sense modsltty. This CONNECTOR description Is not part oF the definition of the word 'open'. It is specific Knowledge that people have about what it means to say that a ~ottle IS open.</Paragraph>
      <Paragraph position="5"> In striving at the ~bove representation, the program must retrieve From memory this OF description of what it means For a bottle to be open. This information is stored Peneath its prototype For bottles. Presumably, there Is also script-like information about the different methods For opening bottles, the different types of caps (corks, twist-off, ...), and which method is appropriate For which cap. However, For the purpose of understanding a text which does not re/er to a specific type of bottle, asp, or opentn~ procedure, what is important is the information aoout how the bottle can  then be used once it is opened. This is the kind of knowledge that OOJect Primitives were designed to capture.</Paragraph>
      <Paragraph position="6"> When the analyzer builds the state description of the bottle, a general demon associated with new state descriptions is triggered. This demon is responsible for updating memory by adding the new state information to the token in the ACTOR slot of the state description. Thus the bottle token is updated to include the gtven CONNECTOR description. For the purposes of this program, the bottle is then considered to be an &amp;quot;open&amp;quot; bottle. A second function of this demon is to set up explicit expectations for future actions based on the new information. In this case, templates for three actions the program might expect to see described can be constructed from the three partially specified conceptualizations shown above In the CONNECTOR description of the open bottle. These templates are attached to the state descrJptlon as possible consequences of that state, for use when attempting to infer the causal connections between events.</Paragraph>
    </Section>
    <Section position="2" start_page="54" end_page="54" type="sub_section">
      <SectionTitle>
3.2 CONCEPT DRIVEN INFERENCES
</SectionTitle>
      <Paragraph position="0"> The phrase &amp;quot;so ne could pour the wine.&amp;quot; Is analyzed as eJohn~ ~.&gt; enable PTRANS &lt;- ewinee &lt;~_&gt;F ?X i</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>
Download Original XML