<?xml version="1.0" standalone="yes"?>
<Paper uid="A88-1017">
  <Title>Structure from Anarchy: Meta Level Representation of Expert System Propositions for Natural Language Interfaces. 1</Title>
  <Section position="4" start_page="121" end_page="122" type="intro">
    <SectionTitle>
LIFER-LADDER (Taken from \[Tennmt 81\])
</SectionTitle>
    <Paragraph position="0"> On the other hand, an expert system is designed to be a problem solver. A use~ consults it about an issue and it must gather information in order to advise him. In figure 2 we present a typical interaction between a user and the Mycin \[Shortliffe 76\] system (taken from transcripts generated by the author). First, in questions 1-6 the system gathers information about the patient, such as age, sex, lab analysis, etc., and then, after many more questions not shown in the figure, makes a recommendation based on the gathered data. Note that the menu interface predefines the order in which information is entered into the system, whereas with a natural language interface, information is entered in no particular order, i.e it may be imbedded in every user input. The addition of new information with every user statement means that the expert system has to pose fewer questions and that the natural language interface must be responsible for managing all the new information. Further, the interface may have to derive information not only from user statements, but also from questions. This means that it has to derive the problem to solve, as well as facts that can be used for its solution from any given question, and add these facts to the data base (or working memory).</Paragraph>
    <Paragraph position="1"> The action of extracting a goal 5 and adding facts at the same time has no analogy in a data base system, but would be similar to allowing the user to query and UlXiate the data base at the same time.</Paragraph>
    <Paragraph position="2">  ~'hmugheut thht paper seth refer to the grab the expert system mutt prove, not Ion 8 tam met goal,.</Paragraph>
  </Section>
class="xml-element"></Paper>