File Information

File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/94/w94-0321_metho.xml

Size: 32,654 bytes

Last Modified: 2025-10-06 14:13:53

<?xml version="1.0" standalone="yes"?>
<Paper uid="W94-0321">
  <Title>Recognizing Digressive Questions During Interactive Generation *</Title>
  <Section position="4" start_page="0" end_page="181" type="metho">
    <SectionTitle>
2 Digression Types
</SectionTitle>
    <Paragraph position="0"> The first and simplest kind of digression that IDP can detect is when the listener asks a direct question about a proposition that was expressed by the system earlier in the discourse. The following interaction demonstrates this kind of digression and how the system responds to it. 1 i , .</Paragraph>
    <Paragraph position="1">  L: Should I take Maple or Sheridan to go to the Eastern Hills Mall? IDP: if now there was light traffic, you could take Sheridan however, now there is heavy traffic.</Paragraph>
    <Paragraph position="2"> you should take Maple.</Paragraph>
    <Paragraph position="3"> since taking Maple there are fewer businesses than taking Sheridan, taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="4"> L: Why is there heavy traffic now? * IDP: since now is rush hour, as I was saying taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="5"> As part of IDP's advice, it has expressed a proposition that lets the listener know circumstances that motivate the advice. In particular, IDP has told the listener that now there is heavy traf:fic. The system identifies the listener's question about this statement (marked with an asterisk) as a digression from the discussion purpose. Therefore, after answering the question, IDP shifts the discussion back to its recommendation.</Paragraph>
    <Paragraph position="6"> A second kind of digression that IDP can detect is when the listener questions a proposition that was never expressed, but that can be inferred from a proposition that has been presented. The following demonstration illustrates this digression type.</Paragraph>
    <Paragraph position="7"> ~he listener's line of questioning keeps referring to the last proposition that was expressed. This eventually leads to an explanation that does not address IDP's original purpose. The following interaction illustrates digressions of this kind.  IDP: taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="8"> L: Why? IDP: taking Maple there are fewer businesses than taking Sheridan.</Paragraph>
    <Paragraph position="9"> L: Why? * IDP: since taking Maple is a newer route than taking Sheridan.</Paragraph>
    <Paragraph position="10"> anyways, taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="11"> Unlike the first two questions, the listener's third why-question requires an answer that cannot be incorporated into the IDP's text plan, a plan for trying to convince the listener to use the Maple Road route. Therefore, the system detects a digression.</Paragraph>
  </Section>
  <Section position="5" start_page="181" end_page="182" type="metho">
    <SectionTitle>
3 Related Work
</SectionTitle>
    <Paragraph position="0"> IDP: taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="1"> L: Why? IDP: since taking Maple there are fewer businesses than taking Sheridan.</Paragraph>
    <Paragraph position="2"> L: Why is there heavy traffic now? * IDP: since now is rush hour, as I was saying taking Maple avoids heavy traffic.</Paragraph>
    <Paragraph position="3"> IDP uses its text plan to detect that the listener's third question, unlike the listener's first two questions, initiates a digression. This is notwithstanding the fact that the system never expressed the proposition that the listener questions. The listener's digressive question relies on an inference that she made from the proposition that IDP conveyed in its second response.</Paragraph>
    <Paragraph position="4"> IDP does not analyze every question as a digression. Demonstration 2a: L: Should I take Maple or Sheridan to go to the Eastern Hills Mall? IDP: take Maple.</Paragraph>
    <Paragraph position="5"> L: Why is there heavy-traffic now? * IDP Huh? In this example, IDP fails to make any coherent connection between the question and the text plan that they system has used so far. Note that the answer to this question does not fall outside the system's expertise. In Demonstration 2, IDP analyzed this question as a digression, and responded to it.</Paragraph>
    <Paragraph position="6"> A third type of digression that the system detects is when Moore and Swartout note that prior to their work on the EES Text Planner, little work had been done on using a sYstem's goals and plans as a model of the discourse and its purpose \[11, 12\]. The EES Text Planner records its discourse goals and the plans that it formulates to achieve them in a dialogue history. When the user asks a follow-up question, the system uses the goal structure of its text plan, assumptions that have been made during generation, and alternative plans that it did not use to disambiguate the question and select a perspective for the answer to it. Then the system formulates the appropriate discourse goal and passes it to the text planner to formulate a response. The dialogue history is a stack of text plans from previous exchanges. Each text plan in the stack has a pointer to a goal (called the global contex 0 that the text plan has been constructed to achieve. However, the stack ordering is the only relationship among the text plans and their respective goals. There is no representation of the overarching goal for the interaction nor how the plan for each exchange contributes to it. Therefore, the system cannot detect when the user's follow-up question results in planning for a discourse goal that does not contribute to the original discussion purpose. null The IDP model treats the system's text plan as a richer source of information. To produce answers to follow-up questions, IDP replans or expands a single text plan that has an overarching discourse goal. In this respect, IDP is similar to the Explanatory Discourse Generator (EDGE) \[2\]. EDGE plans tutorials by formulating a single text plan in advance and then executing it incrementally. EDGE uses feedback from the listener to monitor the success of its plan thereby making decisions to prune or extend parts of it that have not been used yet.</Paragraph>
    <Paragraph position="7"> Planning text ahead is appropriate when a system plans tutorials. In this situation the system has a structure of</Paragraph>
    <Section position="1" start_page="182" end_page="182" type="sub_section">
      <SectionTitle>
7th International Generation Workshop * Kennebunkport, Maine * June 21-24, 1994
</SectionTitle>
      <Paragraph position="0"> preset goals for the interaction. In contrast, IDP is designed for domains where there is no agenda for what the listener will come to know as a result of the interaction. IDP plans text to give advice and answer questions until the listener is satisfied. Therefore, like the EES Text Planner, IDP plans only in reaction to foll0w-up questions. However, to keep track of where the interaction is going, each plan that IDP constructs extends a single text plan that is formulated to achieve an overarching discourse goal.</Paragraph>
    </Section>
  </Section>
  <Section position="6" start_page="182" end_page="183" type="metho">
    <SectionTitle>
4 Text Plan Operators
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="182" end_page="182" type="sub_section">
      <SectionTitle>
4.1 The Planning Formalism
</SectionTitle>
      <Paragraph position="0"> IDP's text plan operators (TP-operators) are based on Rhetorical Structure Theory (RST) \[9\] and are written using the SNePS Actor planning formalism \[16\]. In RST, each essential text message (called the nucleus) can be augmented with additional information (called the satellite) through a rhetorical relation. In the SNePS Actor planning formalism, plan operators are written as rules that state what consequent propositions can be deduced from a set of antecedents.</Paragraph>
      <Paragraph position="1"> Figure 1 shows a TP-operator for the motivate act. ~ In the formalism, an act decomposes into one or more structures of other acts called plans. IDP deduces propositions that state how acts decompose into plans (ACT-PLAN case frame) by satisfying a rule's antecedents. These are the constraints on the plan, and the process of constraint satisfaction selects new content for the text. For TP-operators that are based on rhetorical relations, this new content is a satellite proposition that is appropriate to the rhetorical relation and the given nuclear proposition. The same constraints are used to write rules for deducing the preconditions of the motivate act (ACT-PRECONDITION case frame), the effects of the act (ACT-EFFECT case frame), and the goals that the act (viewed as a high-level plan) can be used to achieve (GOAL-PLAN case frame).</Paragraph>
      <Paragraph position="2"> The TP-operator in Figure 1 is an asserted rule (indicated by !) stating that for all (FORALL) ?gl, ?g2, and ?p, if the antecedents (ANT) can be satisfied, then the consequent proposition (CQ) can be deduced. The TP-operators are domain-independent because the constraints on them are stated in terms of the planning formalism. Hence, IDP's TP-operators are for producing text about a set of domain plans that are under discussion.</Paragraph>
      <Paragraph position="3"> In Figure 1, the constraints are that ?gl must be a goalact, act ?gl must be enacted by a plan ?p, ?g2 must be a secondary goal-act, and act ?g2 must also be enacted by plan ?p. If an instantiati0n of ?gl, ?g2, and ?p satisfies the constraints, then the system can deduce a plan for the act of motivating the user to do ?p. This plan is a sequence (snsequence) of four other acts. The snsequence act is one of six control acts that are used to structure several acts into a plan for an act.</Paragraph>
    </Section>
    <Section position="2" start_page="182" end_page="183" type="sub_section">
      <SectionTitle>
4.2 The Kinds of Text Plans
</SectionTitle>
      <Paragraph position="0"> IDP uses two types of text plans (TPs) separating those plans that address the system's discourse goat (DG) directly, from those plans that provide additional information that augments the system's essential text message. The two  kinds of TPs are discourse text plans (DTPs) and content-selection text plans (CTPs). The overarching plan is always a DTP. This is consistent with Moore and Pollack's contention that a speaker always structures information in a discourse with an high-level intention in mind \[14\].</Paragraph>
      <Paragraph position="1"> This division is based on a two-way division of the rhetorical relations that Mann and Thompson describe and that has been used by Haller \[5, 6\] and Moore and Paris \[13\] to design systems with two types of text plans. Each presentational relation relates two text spans for the purpose of increasing an inclination in the hearer. In contrast, a subject-matter relation is used with the intent of informing the hearer of the rhetorical relation itseIPS In the IDP model, DTPs are used to attempt and reattempt the achievement of the system's discourse goals (DGs). Since these goals have to do with affecting the listener's attitudes and abilities towards domain plans, DTPs are based on speech acts and presentational rhetorical relations. The DTPs describe how to try to achieve DGs by selecting some minimal text content. IDP can augment this content without detracting from its own intent by using one or more CTPs. Therefore, CTPs correspond to subject-matter rhetorical relations.</Paragraph>
      <Paragraph position="2"> Figure 2(a) shows a DTP for motivate that IDP instantiates from the TP-operator given in Figure 1.3 The motivate act takes the listener and a nuclear clause (the listener DOing the *Maple-plan) as its arguments. The DTP for motivating the listener to take the Maple Road route sequences up to four other acts. The first act in the sequence, advise, is another DTP that must be expanded if the system has not already used it. The third act, say, is the only primitive act. When the system executes it, a text message is sent to IDP's surface generation grammar. The second and fourth acts, circumstantiate and restate, are references to CTPs that are potential plan growth points. Growth points are references to CTPs that are embedded in the body of each TP along the active path. Growth points suggest ways of adding content that augment the current TP \[7\].</Paragraph>
      <Paragraph position="3"> A plan for circumstantiate is given in Figure 2(b). Since CTPs are not executed to affect the listener in any way other than to provide information, the listener is not an argument to acts for CTPs. IDP can only deduce a CTP for an act when there is an active content-goal (CG) that the plan satisfies. A constraint on all CTP-operators requires there to be an active CG to let the listener know the proposition that will be the satellite in a subject-matter rhetorical relation.</Paragraph>
      <Paragraph position="4"> As shown in Figure 2(b) as the second step in executing S'Maple-plan represents a plan structure stated in terms of going and turning acts that is not shown here.</Paragraph>
      <Paragraph position="5">  the circumstantiate CTP, the CG is retracted (disbelieved by the system). Because the ACT-PLAN proposition is deducible only when the CG exists, the SNePS Belief Revision component (SNeBR) \[10\] retracts the ACT-PLAN proposition from the knowledge base as part of the execution of the CTP. Unless there is an active CG the CTP cannot be deduced. This keeps the CTP from being expanded and used even though it appears in the body of DTPs like the one for the motivate act (Figure 2(a)).</Paragraph>
    </Section>
  </Section>
  <Section position="7" start_page="183" end_page="184" type="metho">
    <SectionTitle>
5 The Analyzer
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="183" end_page="183" type="sub_section">
      <SectionTitle>
5.1 The Discourse Context
</SectionTitle>
      <Paragraph position="0"> To make the several sources of information that are needed for highly interactive explanations available, I represent them uniformly using the SNePS Semantic Network Processing and Reasoning System \[15\]. IDP's DGs are unachieved system goals that have to do with the attitude or abilities of the listener toward a domain plan. In the role of the primary speaker, IDP can post one or both of the following DGs:  1. to have the listener adopt a domain plan 2. to have the listener be able to execute a domain plan IDP plans text to try to achieve its DG, and it interprets the listener's feedback in the context of three types of knowledge that are all related to its TP: 1. the active path 2. growth points 3. the localized unknowns Following Carberry, once the listener knows the system's  intention and how it has been realized, she has expectations for what will follow \[1\]. Motivated by Grice's Maxim of Relation \[3\], IDP analyzes questions using growth points on the active path. The active path marks the TP that make up the most recent expansion of IDP's overall TP. IDP also uses a set of propositions called the localized unknowns. The localized unknowns are propositions about domain plans and domain-related reasoning that, based on the model of the listener, the listener does not know. The localized unknowns are linked to the system's TP by the reasoning chains that the system used to derive it TP.</Paragraph>
    </Section>
    <Section position="2" start_page="183" end_page="183" type="sub_section">
      <SectionTitle>
5.2 The Local Topic
</SectionTitle>
      <Paragraph position="0"> In the IDP model, questions address the system's DG indirectly by making reference to what the system is doing to achieve its DG. Therefore, IDP's Analyzer uses feedback to try to recognize a TP to use to expand or replan its current TP. Following van Kuppevelt, the local topic is that which is questioned, and the comment on the local topic is an answer to the question \[18\]. For each question, IDP's Analyzer determines the local topic and then searches for a way to expand its TP to include a comment on it.</Paragraph>
      <Paragraph position="1"> The Analyzer processes questions in one of the following forms:  1. Why {not}? 2. Why {not} plan? 3. Why {not} proposffion? {not} indicates that the word &amp;quot;not&amp;quot; is an optional con- null stituent of the input string. The local topic is a domain plan or a proposition. When there is a simple why-question (1), the local topic is the last proposition that was expressed by the system with a say-act. If the question is in the form of 2 or 3, IDP makes the plan or proposition that is mentioned the local topic.</Paragraph>
    </Section>
    <Section position="3" start_page="183" end_page="184" type="sub_section">
      <SectionTitle>
5.3 A Measure of Coherence
</SectionTitle>
      <Paragraph position="0"> From the generation perspective, a conversation is a communicative process that the system controls for its own purpose. In this context, the appropriate measure of coherence is the degree to which a new TP-expansion contributes to the achievement of the system's goal. Discourse expectation constrains IDP's choices to the growth points in the DTPs along the active path. An important heuristic in selecting a TP-expansion is the degree to which the proposed expansion highlights the system's intent as realized by the DTP-level portion of its TP. Therefore, IDP considers the growth points for the DTPs on the active path in the fol- null lowing order: 1. DTPs that replan a DTP 2. CTPs that expand a DTP  IDP prefers DTPs that replan a DTP over CTPs that expand a DTP. This encodes a preference for plans that highlight the system's intent over plans that supply additional information.</Paragraph>
      <Paragraph position="1"> In the first phase, IDP analyzes why-questions in relation to its own intent as represented by the DTPs along the active path. The Analyzer starts with the most recently executed DTP (the last DTP on the active path), and the localized unknowns associated with it. It tries to find another way to expand a DTP along the active path that lets the listener know a localized unknown. The Analyzer backs up the active path testing each DTP in turn. If this fails, in the second phase, the Analyzer considers augmenting the existing DTP at the informational level. This level is reflected in the CTPs. The Analyzer examines the most focussed DTP on the active path to see if it can he expanded with a CTP to let the user know a localized unknown. A detailed account of this type of processing is presented in \[5\].</Paragraph>
      <Paragraph position="3"/>
    </Section>
    <Section position="4" start_page="184" end_page="184" type="sub_section">
      <SectionTitle>
5.4 An Example TP
</SectionTitle>
      <Paragraph position="0"> Figure 3 shows IDP's TP after its third response in Demonstrations 2 and 3. The TP has been formulated to achieve the DG of having the listener adopt the plan to take Maple Road. The high-level plan is a DTP which can decompose into other DTPs and CTPs. The TP always bottoms out in the primitive act, say. The argument to the say act is a text message which includes a proposition as the content to be expressed.</Paragraph>
      <Paragraph position="1"> In the TP, the checks (x/) mark the active path. Note that the plan for motivating the listener has not been executed in the order indicated by the sequencing act snsequence (see Figure 2(a))i In particular, to make the initial recommendation the planner selected a simple plan (advise, indicated by a dashed line) over a more complex plan (motivate). In response to the listener's first why-question, IDP replanned the recommendation with the more complex motivate act. Since its recorded TP indicated that it had just used the advise act, the only act in the plan for the motivate act that must be executed is the say act. This act conveys the satellite proposition ~that counts as the motivation for the advice.</Paragraph>
      <Paragraph position="2"> The second act in the plan for motivate, circumstantiate expands to an optional CTP. IDP does not expand and use this plan until it responds to Why? a second time. This happens because IDP replans and expands its TP in reaction to the listener's questions.</Paragraph>
    </Section>
  </Section>
  <Section position="8" start_page="184" end_page="187" type="metho">
    <SectionTitle>
6 Detecting Digressive Questions
</SectionTitle>
    <Paragraph position="0"> If the Analyzer fails to recognize a way to replan Or expand its own TP from the listener's feedback (Section 5.3), it tests the feedback to See if is a digressive question. Figure 4 gives the algorithm that the Analyzer uses for the IS-DIGRESSION test. :The Analyzer tests the feedback (fb) in two stages. First, the Analyzer tests to see if the feedback has the correct form and content for one of three kinds of digressive questions that the system can detect. If one of the three tests succeeds, it will return a proposition that is the topic (topic) for the digression. The topic is the proposition that the listener questions in her digressive  performed that is related to the topic (related-reasoning).</Paragraph>
    <Paragraph position="1"> The Analyzer tests each CTP and removes any CTPs that have the effect of letting the listener know a proposition that she knows already. It also removes a CTP if its effect is not one of the related reasoning propositions. If there is still more than one candidate CTP, the Analyzer picks the simplest (ctp-to-expand). If a CTP has been found that meets all of the requirements, the Analyzer posts its effect as a CG and returns it for the Planner-Actor to expand to answer the question. If there is no such CTP, then the digression test fails.</Paragraph>
    <Section position="1" start_page="184" end_page="185" type="sub_section">
      <SectionTitle>
6.1 Detecting Digressive Questions About
What has been Said
</SectionTitle>
      <Paragraph position="0"> The simplest kind of digression that IDP can detect is when the listener asks a direct question about a proposition that was expressed as part of the system's TP. The Analyzer uses the first digression test, IS-DIGRESSION-TYPE-I, that is described in Figure 5. If the feedback (fb) is a question in the form &amp;quot;Why&amp;quot; {&amp;quot;not&amp;quot;} proposition and the system has said the proposition as part of its TP, then the proposition is returned as the topic for the digression. Otherwise, the first test fails.</Paragraph>
      <Paragraph position="1"> The first test is used to detect the digression in Demonstration i. Figure 6 gives IDP's TP just before the listener asks the digressive question in that example. When the listener asks Why is there heavy traffic now?, the Analyzer tries to find a way to expand the DTP-portion of its</Paragraph>
    </Section>
    <Section position="2" start_page="185" end_page="185" type="sub_section">
      <SectionTitle>
7th International Generation Workshop * Kennebunkport, Maine * June 21-24, 1994
</SectionTitle>
      <Paragraph position="0"> TP on the active path (Section 5.3). This involves searching the growth points in the DTPs for motivate, concede, and recommend. When this fails, the Analyzer tries to process the feedback as a digressive question.</Paragraph>
      <Paragraph position="1"> Testing for a digression (Figure 4) with the first digression rule (Figure 5), the Analyzer checks the TP in Figure 6 to see if the proposition in the listener's question was said by the system. The Analyzer finds that it has been said (Figure 6 in boldface). Therefore, the first digression test succeeds, and the following proposition is returned as the topic of the digression: OBJ-PROP(now, heavy-traffic) The Analyzer finds another CTP that uses the topic as a nucleus: circumstantiate(OBJ-PROP(now, heavy-traffic)) and collects reasoning that is related to the topic ACT-PLAN(avoid(heavy-traffic), *Maple-plan) OBJ-PROP(now, rush-hour)) SECO N DARY-GOAL-ACT(avoid(heavy-traffic)) The CTP's effect, KNOW(listener, OBJ-PROP(now, rush hour)) lets the listener know a new satellite proposition: now is rush hour. Since (he listener model does not assert that the listener knows this proposition, and since this proposition is related by domain reasoning to the topic, the CTP remains as a candidate for expansion. So that IDP's Planner-Actor can instantiate a plan for this CTP, its effect is made a CG. Then the CTP is returned for the Planner-Actor to expand into the TP. This leads to the restatement found in the last line of IDP's response in Demonstration 1.</Paragraph>
    </Section>
    <Section position="3" start_page="185" end_page="186" type="sub_section">
      <SectionTitle>
6.2 Detecting Digressive Questions About
Inferred Propositions
</SectionTitle>
      <Paragraph position="0"> In Demonstration 2, IDP never expressed the proposition that the listener questions. Therefore, the listener must have inferred it. In this case, the system cannot determine that the question is digressive simply because the answer is something that the listener does not know. Such a rule would not distinguish digressive questions from incoherent ones.</Paragraph>
      <Paragraph position="1"> To test for digressive questions about propositions that the listener has inferred, the Analyzer uses the second test, IS-DIGRESSION-TYPE-2, that is described in Figure 7. The Analyzer checks to see if the feedback is a why-question about a proposition (proposition) that has not been expressed by the system, but that can be inferred (IS-INFERABLE) from what has been said. If the proposition satisfies these requirements, then, as in the previous case, the proposition is returned as the topic for the digression. Otherwise, the second test fails.</Paragraph>
      <Paragraph position="2"> A question is coherent only if the listener has inferred it correctly from something that the system has said. Figure 8 describes the test, IS-INFERABLE, that the Analyzer uses to determine if the questioned proposition is inferable. First, the Analyzer gathers all the propositions that IDP has said as the content of a say act (expressed-props).</Paragraph>
      <Paragraph position="3"> For each expressed proposition (prop), the Analyzer collects propositions that are within two reasoning steps of  each expressed proposition. These are added to the propositions that are inferable (inferable-props). Some of the propositions that can be inferred may have been said already. Therefore, after collecting the inferable propositions, the Analyzer removes any proposition that is also one of the expressed propositions. FinMly, the Analyzer checks to see if the proposition that the listener has questioned is among those that are unsaid, but inferable, from what IDP has said previously. If it is, the test succeeds.</Paragraph>
      <Paragraph position="4"> In Demonstration 2, the second digression test is used to help determine that the listener's question is digressive. Figure 3 gives the system's TP just before the digressive question Why is there heavy traffic now?. In this interaction, the questioned proposition has not been expressed by the system. Therefore, the first digression test (Figure 5) fails immediately. In the second digression test (Figure 7), the form of question is satisfactory and the system has not expressed the questioned proposition.</Paragraph>
      <Paragraph position="5"> Therefore, IS-INFERABLE is invoked to see if the proposition null OBJ-PROP(now, heavy-traffic) can be inferred from what has been said.</Paragraph>
      <Paragraph position="6"> At this point in the discourse, the propositions that IDP has expressed with say acts are DO(listener, *Maple-plan) ACT-PLAN(avoid(heavy traffic), *Maple-plan) FEWER-BUSINESSES(*Maple-plan, *Sheridan-plan) The Analyzer collects unsaid propositions that are related by reasoning to them.</Paragraph>
      <Paragraph position="7"> OBJECT-PROP(now, heavy-traffic)</Paragraph>
      <Paragraph position="9"> These are the inferable propositions. Since the questioned proposition is among them, the test for the second type of digressive question succeeds.</Paragraph>
      <Paragraph position="10"> Next, the Analyzer tries to find a CTP that uses the proposition as a nucleus (Figure 4). As before, the CTP that it finds is circumstantiate(OBJ-PROP(now, heavy-traffic)) Since the listener does not know its effect, the Analyzer selects the CTP to answer the digressive question by making its effect a CG, and returning the CTP to be expanded and executed by the Planner:Actor.</Paragraph>
    </Section>
    <Section position="4" start_page="186" end_page="186" type="sub_section">
      <SectionTitle>
6.3 Detecting Garden-path Digressions
</SectionTitle>
      <Paragraph position="0"> Demonstration 3 shows that when the listener repeatedly asks Why?, IDP eventually recognizes a garden-path digression. A garden-path digression will always occur at some point in an interaction, if the listener asks a series of simple why-questions. The test is a simple one that is given in  test succeeds and the last proposition that was expressed is returned as the topic of the digression.</Paragraph>
      <Paragraph position="1"> In Demonstration 3, When the listener asks Why? a third time, the state of IDP's TP is the same as in Demonstration 2 (Figure ??). The first two digression tests fail because the form of the question is incorrect. Using the third digression test (Figure 9), the last proposition that the system expressed, and therefore, the topic of the digression becomes  The effect of the CTP is to let the listener know the second proposition above. Since the listener does not know this proposition, and since it is reasoning that is related to the topic, the CTP remains as a candidate for answering the digressive question (Figure 4). After asserting that the effect of the CTP KNOW(listener, NEWER-ROUTE(*Maple-plan, *Sheridan-plan)) is a CG, the Analyzer returns it to be expanded to answer the digressive question. In Demonstration 3, this results in the system response: since taking Maple is a newer route than taking Sheridan.</Paragraph>
    </Section>
    <Section position="5" start_page="186" end_page="187" type="sub_section">
      <SectionTitle>
6.4 Incoherent Questions
</SectionTitle>
      <Paragraph position="0"> In the IDP model, an incoherent question is a question that cannot be related to the system's TP either by replanning/expanding the system's TP, or by identifying it as a digression. Demonstration 2a shows how IDP processes incoherent questions. When the Analyzer tries to replan or expand its DTP to answer the question (Section 5.3), it</Paragraph>
    </Section>
    <Section position="6" start_page="187" end_page="187" type="sub_section">
      <SectionTitle>
7th International Generation Workshop * Kennebunkport, Maine * June 21-24, 1994
</SectionTitle>
      <Paragraph position="0"> cannot find a TP that uses the propositional content of the question OBJ-PROP(now, heavy-traffic) as a nucleus. Therefore, analyzing the question to recognize a way to extend IDP's TP fails.</Paragraph>
      <Paragraph position="1"> Next, the Analyzer attempts to process the question as a digression (Section 6). IDP answered this question in Demonstrations 1 and 2. In Demonstration 2a, the questioned proposition has not been expressed previously. Therefore, the first digression test fails immediately. The third digression test also fails because the question is not a simple why-question. In the second digression test, the utterance satisfies the first two conjuncts. That is, it has the correct form, and it has not been expressed by the system. However, it is not inferable from what has been said so far. At the point in the discourse where the question is asked, the only proposition that IDP has expressed is DO(listener, *Maple-plan) Since this proposition is not a true fact in the knowledge base, no propositions are inferable from it. Therefore, the Analyzer determines that the questioned proposition is not a digression. Having failed all the tests, IDP responds with Huh?.</Paragraph>
      <Paragraph position="2"> Note that in Demonstration 2a, the proposition that the listener questions OBJ-PROP(now, heavy-traffic) and the answer to it OBJ-PROP(now, rush-hour) are among the localized unknowns (Section 5.1) that can be associated with the TP at the point in the discourse where the question is asked. This means that the information that the listener refers to with her question is highly relevant domain information. In spite of this, the question is incoherent. This suggests that discourse focus and purpose are more important factors for determining the coherency of a question than the domain structure.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>
Download Original XML