File Information

File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/86/p86-1016_metho.xml

Size: 37,949 bytes

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

<?xml version="1.0" standalone="yes"?>
<Paper uid="P86-1016">
  <Title>The ROMPER System: Responding to Object-Related Misconceptions using Perspective 1</Title>
  <Section position="3" start_page="97" end_page="97" type="metho">
    <SectionTitle>
2 Misconception Responses
</SectionTitle>
    <Paragraph position="0"> The view of natural-language generation taken in this system is the same as that taken in \[McK82\]. The generation process is seen as consisting of two parts: (1) determining the content and structure of the response and producing a formal message specification, and (2) transforming that specification into actual English text. My work has concentrated on determining the content and structure of a response to a misconception. It attempts to automate the process of deciding what information to include in a response to a misconception by giving the system the ability to reason about certain classes of misconceptions and typical ways of correcting misconceptions in one of the identified classes. This should be contrasted with the a priori listing of misconceptions and responses found in most existing systems that handle misconceptions (\[SC80\], \[BB78\], and \[Woo84\]). 2 The form of the responses generated by ROMPER derived from an analysis of transcripts of human conversational partners. These transcripts revealed that responses to statements containing misconceptions often include more than a simple denial of the wrong information. This is particularly true in circumstances where the misconception is about something important to the current goals of the participants. In addition to denying the information involved in the misconception, many misconception responses include both the corresponding correct information, and additional justification for the denial and correction given. The justification often involves refuting faulty reasoning that may have led the user to the misconception.</Paragraph>
    <Paragraph position="1"> While it may seem that the kinds of faulty reasoning that the user may be using to arrive at a misconception are limitless, the transcript analysis revealed a surprisingly small number of misconception support relations that are refuted by the human experts. In addition, these few misconception support relations can be couched in terms of a knowledge base (KB) structure rather than its content. Thus a system reasoning on a model of the user might look for such relations in a domain independent fashion. If one is found, information refuting the misconception support might be included in the corrective response.</Paragraph>
    <Paragraph position="2"> To see this, let us examine the number of ways that a human expert was found to correct one of the misconception types handled by ROMPER: misclas~ifications. The strategies used by the human experts to respond to a miselassification can be exemplified by the number of possible responses to the following misconception: U. I thought whales were fish.</Paragraph>
    <Paragraph position="3"> R1. No, they are mammals. You may have thought they were fish because they are fin-bearing and live in the water.</Paragraph>
    <Paragraph position="4"> However, they are mammals since, (while fish have gills) whales breathe through lungs and feed their young with 2\[Woo84\] represents a departure from the canned response in that she is concerned with appropriately structuring a response to reflect a certain tutoring style.</Paragraph>
    <Paragraph position="5"> milk.</Paragraph>
    <Paragraph position="6"> R2. No, they are mammals. You may have thought they were fish since they are like the fish, sharks, in that both are large aquatic creatures and both scare people. However, whales are mammals since, (while fish have gills) whales breathe through lungs and feed their young with milk.</Paragraph>
    <Paragraph position="7"> R3. No, they are mammals.</Paragraph>
    <Paragraph position="8"> Before analyzing each one of these in detail, let us first note their similarities. Each of the above strategies can be seen as consisting of three parts: (1) a denial of the incorrect classification, (2) a statement of the correct classification, and (3) an offering of justification for the denial/correction pair. This three part strategy is, in fact, typical of all of the responses found in the transcript analysis. Notice that the denial of the incorrect information and the offering of the corresponding correct information is the same in each of the sample responses given. What distinguishes one kind of response strategy from another is the kind of justification given in each case. Responses R1 and R2 offer two different kinds of justi~cation while R3 offers no justification.</Paragraph>
    <Paragraph position="9"> Given that examples of each of the above three kinds of responses were found in the transcripts, we must ask what causes one to be used in preference to another in a particular situation. One explanation is that different beliefs about what the user believes trigger the use of each strategy. Notice that each strategy can be seen as refuting a different kind of support for the misconception. My claim is that a speaker may choose a strategy depending on the support that he/she believes the user may be using to come up with the misconception. Let us take each strategy in turn, examine what beliefs might have led to the use of that strategy, and then investigate how this information might be used by a system to generate responses to misconceptions.</Paragraph>
  </Section>
  <Section position="4" start_page="97" end_page="99" type="metho">
    <SectionTitle>
3 Using Response Strategies
</SectionTitle>
    <Paragraph position="0"> The justification in R1 consists in the expert conceding properties that whales have in common with fish (fin-bearing and water-living), and overriding that conceded information with properties that distinguish whales from fish. The use of this strategy by an expert might be explained by the expert believing that the user believes that whales and fish are similar, and that that similarity may have led to the misclassification.</Paragraph>
    <Paragraph position="1"> An expert having these beliefs might very well find it reasonable to concede that the similarity between whales and fish does indeed exist, but then go on to show that that similarity is not enough to classify whales as fish. S/he may do this, as above, by offering properties that make whales mammals instead of fish.</Paragraph>
    <Paragraph position="2"> Given that this analysis might explain a human's response to a misconception, we might have a computer system  adopt this strategy to respond to a misconception in a natural way. First, the information included in a response like R1 can be captured in a response schema as shown below. R1 can be seen as an instantiation of this schema where OBJECT is instantlated with whale, POSITED with fish, and REAL with mammal. The shared attributes are instantiated in the obvious way.</Paragraph>
    <Paragraph position="3">  The above schema is called the =like-super&amp;quot; schema because it is used by ROMPER when the user exhibits a misconception by wrongly classifying some OBJECT as a POSITED superordinate and when ROMPER determines that a probable reason for the miaclassification is that the user believes that the OBJECT and the POSITED superordinate are similar to each other. The schema captures a response like R1 by specifying a denial of the incorrect classification, a statement of the correct classification, and then an offering of justification. The justification is in the form of conceding the similarity that may have led to the miaclassification (e.g., the shared attributes), but overriding that conceded information with attributes that are not shp-ed by the OBJECT and the POSITED superordlnate but instead distinguish the two.</Paragraph>
    <Paragraph position="4"> It should be pointed out that this schema encodes two kinds of information: a domain-independent specification of the content of each proposition included in the response (e.g., an object classification or shared attributes between objects), as well as information about the rhetorical force or communicative role played by each proposition (e.g., a denial or statement or conceded information). The content specification is derived from the transcript analysis. The rhetorical force is derived from both the transcript analysis and from work done by \[McK82\], \[MT83\], and \[Man84\] who have developed theories about the role that a proposition can play in a discourse. The goal in using such a schema is to have a specification of a response that may be filled in with information from the user model and that, when instantiated, contains enough rhetorical information to be turned into a cohesive English text by a tactical component. The schema above meets both of these requirements.</Paragraph>
    <Paragraph position="5"> The justification included in R2 is also in the form of a concede/overrlde pair. However, in the case of R2, rather than concede a similarity between whales and al___l fish, a similarity between whales and some subset of fish (i.e., the sharks) is conceded. The use of this response might be explained by the expert believing that the user believes whales and sharks to be similar and salient at this point in the discourse. The expert might imagine the user to have reasoned: &amp;quot;I don't know how to classify whales, but I do know that they are similar to sharks and I know that sharks are fish. Perhaps whales are fish as well.&amp;quot; This analysis was used in developing ROMPER by associating a schema based on responses like R2 with a user model configuration showing a similarity between the misclassifled object and some descendent of the posited superordinate. The schema is termed the &amp;quot;llke-some-super&amp;quot; schema and is shown  Response R3 can be thought of as the degenerate strategy since it contains no justification for the denial/correction pair. ROMPER instantiates the schema corresponding to R3 when neither of the two above mentioned knowledge base configurations can be found in the user model.</Paragraph>
    <Paragraph position="6"> So far this paper has concentrated on mlselassifications.</Paragraph>
    <Paragraph position="7"> ROMPER also handles mlsconceptions involving an object's attributes. The transcript analysis revealed three correction strategies for misattributions as exemplefied by the following responses:  U. What is the interest rate on this stock? R4. Stock doesn't have an interest rate. Were you thinking of a bond? RS. Stock doesn't have an interest rate. Did you mean dividend? null R6. Stock doesn't have an interest rate.</Paragraph>
    <Paragraph position="8">  ROMPER employs three correction schema to handle misattributlons; one for each of the response strategies shown. R4 can be seen as in instantiation of ROMPER's wrong-object schema. This schema offers an object which has the attribute involved in the misconception that the user may have either confused with the misconception object or made a bad analogy from. It is instantiated when an object is found that has the attribute involved in the misattribution and is similar to the misconception object.</Paragraph>
    <Paragraph position="9"> R5 exemplifies the wrong-attribute schema which offers an attribute that the object involved in the misconception does  have. This response is used when there is reason to beLieve the user may have confused the attribute involved in the misconception with a similar attribute that the object does have. ROMPER uses the schema when the misconception object has an attribute that is similar to the attribute involved in the misconception. null As is the case with the misclassifications, there is a ~degenerate&amp;quot; schema for misattributions. This schema contains no justification for the correction and is exempLified by R6. In summary, a study of transcripts of humans responding to misconceptions reveals a great deal of regularity in the way misconceptions about objects are corrected. One can abstract a small number of response strategies for each of the various knowledge base features that might be involved in a misconception. Each of these strategies can be seen as refuting a different kind of support that the user may have for the information involved in the misconception. These strategies are captured as schemas in the ROMPER system and each schema is associated with a domain independent description of the kind of support it refutes. ROMPER, when faced with a misconception, operates on a model of the user looking for evidence for one of the identified kinds of support. If enough evidence is found, the response to the misconception is generated by instantiating the corresponding schema.</Paragraph>
  </Section>
  <Section position="5" start_page="99" end_page="99" type="metho">
    <SectionTitle>
4 Effects of Context
</SectionTitle>
    <Paragraph position="0"> The above section outlined a method for correcting misconceptions. While the method does seem to be appealing, at first glance it seems to have a major flaw. It does not seem to take into account the role that previous context plays in correcting misconceptions. The responses given by the human experts were very context dependent. In two different contexts a human expert might choose to correct the same misconception by the same user in two different ways. For example, in response to the misconception exhibited by ~I thought whales were fish &amp;quot;, an expert might choose R1 in one context and R2 in another. How can this be explained if the process described above is used to respond? I claim that the process of correcting misconceptions is context sensitive not because the process changes with context, but because what the process works on changes with context. In particular the piece of the user model that is analyzed in looking for possible sources of the misconception changes with context.</Paragraph>
    <Paragraph position="1"> Instead of doing the user model analysis on a flat representation containing everything that the user knows at equal levels of importance, the analysis is done on a model that has been highlighted by previous discourse. Previous discourse serves to highlight certain aspects of the user model while suppressing others. Different highlighting resulting from different previous discourse may cause the user model analysis to conclude that different support had been used for the misconception and therefore cause a different response strategy to be selected. Object perspective is a notion which can be used to model this contextual effect.</Paragraph>
  </Section>
  <Section position="6" start_page="99" end_page="103" type="metho">
    <SectionTitle>
5 Object Perspective
</SectionTitle>
    <Paragraph position="0"> In this section I introduce a new notion of object perspective as an augmentation to a standard semantic network representation. Before introducing this notion let us first examine what we want this notion to account for.</Paragraph>
    <Paragraph position="1"> The notion of object perspective has previously been discussed in the Literature. It can be Likened to the ~point of view ~ one takes on an object in a particular discussion. From a particular point of view certain characteristics of the object seem more important than others. For instance, a particular building may be discussed from the point of view of being someones home on the one hand, and from the completely different pont of view of being an architectural work on the other. The two different views of the same building cause different groups of attributes to be important. It is this highlighting of a whole group of attributes that must be explained. Notice that it could not be explained by a focusing mechanism which highlights attributes which have been mentioned in the preceding discourse because many of the highLighted attributes may not have been expLicitly mentioned. What needs to be captured is the feeling that each view calls to mind a ~precompiled&amp;quot; set of attributes that seem to be important while that view is in effect.</Paragraph>
    <Paragraph position="2"> An attempt to explain this effect has been made by defining object perspective as viewing an object as a member of one superordinate when, in fact, it may have many superordinates (\[Gro77\], \[BW77\], and \[TWF*82\]). The highlighting is achieved through a limited inheritance mechanism. An object inherits only those attributes contributed by the one superordinate deemed &amp;quot;in perspective&amp;quot;. Thus, when a building is viewed as an architectural work, for example, it inherits only those attributes associated with the concept architectural-work in the generalization hierarchy. Any attributes that it might inherit from other superordinates (e.g., home) are ignored. While this notion is intuitively appealing, in practice it .is problematic (see \[McC85\] for details) and is unable to handle some additional effects which intuitively should be handled by object perspective.</Paragraph>
    <Paragraph position="3"> Two of these effects will be discussed here.</Paragraph>
    <Paragraph position="4"> During the course of a conversation it is usually the case that more than one object will be discussed. When this happens, usually the same kinds of things are discussed about the objects. In essence, a particular highlighting of attributes (or point of view) seems to be in force during the conversation. Yet, this highlighting is applied to different objects. What seems to be happening is that the conversational partners are viewing an entire group of objects from the same perspective. This cannot be accounted for by the previous definition of object perspective unless each of the objects under discussion can be said to have the same superordinate.</Paragraph>
    <Paragraph position="5"> A second effect which is not accounted for by the above definition, yet seems to hinge on object perspective, has to do  with the heightened importance of some objects during a discourse. For instance, in the responses R1-R3 above, the correct classification of whale was given as mammal. It is the case, however, that whales are cetaceans and cetaceans are marnmais. If the expert above thought that U. knew about cetaceans, why wasn't cetaceans given as the correct classification? Since there was no preceding discourse given in this case, some default context would have to be in force. Apparently, in this context cetacean did not seem important enough to mention. Yet in other contexts, on can imagine cetacean being given as the correct classification even though it had not yet been explicitly referred to in the preceding discourse. The importance of the object cetacean seems to have something to do with the current perspective from which objects are being viewed. The previous definitions of object perspective do not address this issue.</Paragraph>
    <Section position="1" start_page="100" end_page="100" type="sub_section">
      <SectionTitle>
5.1 Perspective: Definition and Representation
</SectionTitle>
      <Paragraph position="0"> I claim that all of the above criteria can be met by a simple notion of object perspective which has the following properties: First, instead of tying perspective into the generalization hierarchy of objects as has been done in the past, the new notion of perspective will be independent of that hierarchy. &amp;quot;Perspectives&amp;quot; which can be taken on the objects in the domain will be defined and will sit in a structure which is orthogonai to the generalization hierarchy.</Paragraph>
      <Paragraph position="1"> Second, the number of such perspectives that need be defined for the objects in a given domain of discourse is small and finite. Moreover, any given domain object may be viewed from any one of several perspectives defined for that domain. As it turns out, it will make more sense to view some of the objects in the domain through some perspectives and not others, but this is a feature of perspectives which will be taken advantage of later.</Paragraph>
      <Paragraph position="2"> Third, each perspective comprises a set of attributes with associated salience values. It is these salience values that dictate which attributes are highlighted and which are suppressed. null Fourth, one such perspective is designated active at a particular point in the discourse.</Paragraph>
      <Paragraph position="3"> This notion of object perspective works as follows. An object or group of objects is still said to be viewed through a perspective. In particular any object which is accessed by the system is viewed through the current active perspective.</Paragraph>
      <Paragraph position="4"> However, instead of dictating which attributes an object inherits, the active perspective affects the salience values of the attributes that an object possesses (either directly or inherited through the generalization hierarchy). The active perspective essentially acts as a filter on an object's attributes - raising the salience of and thus highlighting those attributes which have a high salience rating in the active perspective, and lowering the salience of and thus suppressing those attributes which are either given a low salience value or do not appear in the active perspective.</Paragraph>
      <Paragraph position="5"> The importance of an object in a discourse is determined by the salience values given to the attributes it possesses. The idea is that the whole becomes highlighted by having its parts highlighted. Thus, during a discussion in which the active perspective highlights many attributes contributed by the object &amp;quot;cetacean&amp;quot; in our generalization hierarchy, cetacean will be seen as an important object. If, on the other hand, none of the attributes associated with cetacean are highlighted, then that object will be suppressed.</Paragraph>
      <Paragraph position="6"> This notion of object importance realizes the intuitive notion that it makes &amp;quot;more sense&amp;quot; to view some objects through particular perspectives than others. It makes more sense to view an object through perspectives that highlight many of the object's attributes and thereby make the object more dominant. Notice that we can see a certain amount of symmetry here. The perspective determines the salience of an object's attributes and the object's importance; the object and its attributes determines how likely the object is to be viewed from a particular perspective.</Paragraph>
    </Section>
    <Section position="2" start_page="100" end_page="101" type="sub_section">
      <SectionTitle>
5.2 Using Perspective
</SectionTitle>
      <Paragraph position="0"> A model of a particular domain would include the usual object taxonomy containing all of the objects in the domain and all of the attributes those objects possess. So in our fish-mammal domain we would have sharks as a kind of fish with attributes like &amp;quot;scare-people s and &amp;quot;large-aquatic-creature&amp;quot;. In addition, all of the attributes of fish would also be represented and sharks would inherit those attributes as well.</Paragraph>
      <Paragraph position="1"> In addition to the object taxonomy, we must build a separate structure containing the perspectives that can be taken on the domain objects. One perspective we might imagine defining for the fish-mammal domain would be the &amp;quot;body-characteristics&amp;quot; perspective. In this perspective attributes like &amp;quot;fin-bearing ~, &amp;quot;have-gills&amp;quot;, and &amp;quot;breathe-through.lungs ~ would be given high salience and thus highlighted. Other attributes would be suppressed by this perspective.</Paragraph>
      <Paragraph position="2"> Another perspective that might be defined for the fish-mammal domain might be the &amp;quot;common-people's-perception&amp;quot; perspective. This perspective might highlight attributes like &amp;quot;large-aquatic-creatures ~ and *scare-people&amp;quot;. Other attributes, like &amp;quot;have-gills&amp;quot; and ~fin-bearing&amp;quot; might be suppressed by this perspective.</Paragraph>
      <Paragraph position="3"> ROMPER uses the highlighting from object perspective in two ways. First, during the user model analysis it uses the information to check for user model configurations which might indicate particular kinds of support for a misconception. Section 2 introduced two user model configurations which were associated with response schemas. The like-super schema was associated with a user model configuration that indicated that the user believed the misclassified object was like the posited superordinate. The like-some-super schema was associated with a user model configuration that indicated that the user believed the misclassified object was like some descendent of the poeited  superordinate. Notice that both of these user model configurations hinge on a similarity assessment between objects. The similarity metric used by ROMPER is one that is based on the objects' common and disjoint attributes which takes attribute salience into account \[Tve77\]. This metric will be discussed below. Since the similarity metric takes attribute salience into account and attribute salience is effected by object perspective, the active perspective can influence the selection of a misconception response schema.</Paragraph>
      <Paragraph position="4"> Second, ROMPER uses the highlighting from object perspective to instantiate the selected response schema. It attempts to do this using only attributes deemed important by the current perspective.</Paragraph>
    </Section>
    <Section position="3" start_page="101" end_page="101" type="sub_section">
      <SectionTitle>
5.3 Object Similarity
</SectionTitle>
      <Paragraph position="0"> As was mentioned above, the object similarity metric used by ROMPER must be sensitive to context. To date, most AI systems that use object similarity use a metric that is based on distance in the generalization hierarchy. Such a metric is not context sensitive.</Paragraph>
      <Paragraph position="1"> The ROMPER system uses a similarity metric based on work done in {Tve77\] which allows contextual information to be taken into account. Tversky's metric, called a contrast model, is based on the common and disjoint features/propertles of the objects involved. Suppose we have two objects a and b where A is the set of properties associated with object a and B is the set of properties associated with object b. Tversky's measure can be expressed as:</Paragraph>
      <Paragraph position="3"> for some 0, o~, and fl &gt; 0.</Paragraph>
      <Paragraph position="4"> In the above equation 0, a, and/3 are parameters which alter the importance of each piece of the equation. The function f maps over the features and yields a salience rating for each, In essence, the contrast model states that the similarity of two objects is some function of their common features minus some function of their disjoint features. The importance of each particulax feature involved (determined by the function f) and the importance of each piece of the equation (determined by 0, c~, and fl) may change with context.</Paragraph>
      <Paragraph position="5"> In order to use the metric, we must come up with values for the functions in the equation. Tversky suggests that the 0, c~, and fl functions might be affected by the relative prominence of objects a and b in the discourse. If a is relatively more important, then function 0 and a should be greater than/~ resulting in the attributes of the more prominent object having a greater influence over the similarity assessment. While I would conjecture that information about the focus of the discourse \[Gro81\], \[Sid83\], \[GJW83\] might give an indication of an object's prominence and would therefore be useful in setting the values of 0, ~, and /3, in this work I have assumed a value of 1 for the 0, a, and /3 and have concentrated on setting the f function.</Paragraph>
      <Paragraph position="6"> In the ROMPER system the f function has been set using the salience values returned after the knowledge base has been filtered through object perspective. Using this setting of f the same two objects may be seen as very similar when the active perspective highlights attributes that the objects have in common and suppresses those that are disjoint between them.</Paragraph>
      <Paragraph position="7"> On the other hand, the same two objects may be seen as very different when the active perspective suppresses attributes that they have in common and highlights those that are disjoint between them.</Paragraph>
      <Paragraph position="8"> This similarity metric is used by ROMPER in deciding which schema to use to respond to a particular misconception.</Paragraph>
      <Paragraph position="9"> Suppose that ROMPER must respond to the misconception ~I thought a whale was a fish&amp;quot; when the active perspective is the &amp;quot;body-characteristics ~ perspective defined above. Recall that this perspective highlighted attributes like fin-bearing, havegills, and breathe-through-lungs. Under this perspective, attributes common to whales and all fish are highlighted. Using a Tversky-like similarity metric this highlighting causes whales and fish to be seen as similar. ROMPER would thus respond using the like-super schema producing a response similar to R1.</Paragraph>
      <Paragraph position="10"> If, on the other hand, the same misconception were encountered when the perspective was &amp;quot;common-people'sperception&amp;quot;, the attributes that whales and all fish have in common would not be highlighted. Rather, attributes llke scarepeople and large-aquatic-creatures shared with just a subset of fish, the sharks, would be highlighted. Under these conditions, the similarity metric would return a low similarity rating for whales and all fish (and thus the &amp;quot;like-super ~ schema would not be applicable), but a high similarity rating for whales and sharks. Thus, the &amp;quot;like-some-super&amp;quot; schema would be used to produce a response similar to R2 above.</Paragraph>
      <Paragraph position="11"> One can imagine how other perspectives might make neither the &amp;quot;like-super&amp;quot; nor the ~like-some-super&amp;quot; schemas applicable, causing the &amp;quot;no-support&amp;quot; schema to be used.</Paragraph>
    </Section>
    <Section position="4" start_page="101" end_page="102" type="sub_section">
      <SectionTitle>
5.4 Choosing the Active Perspective
</SectionTitle>
      <Paragraph position="0"> In order for the notion of object perspective to be truly beneficial, there must be a mechanism for choosing the active perspective based on previous discourse. While this topic is still very much open to investigation, some preliminary research has revealed several factors that might influence the choice of active perspective.</Paragraph>
      <Paragraph position="1"> Perhaps one of the most influential pieces of information useful in choosing a perspective is the user's current goal. In \[MWM85\] the user's goal completely determines which perspective is active. In their work each perspective which can be taken on the domain objects is indexed by potential goals. Thus, once the system has determined what the user's goal probably is, it has also determined what perspective the user has probably taken on the domain objects.</Paragraph>
      <Paragraph position="2"> While it is true that the user's goal is a good source of information to use to determine the probable perspective,  other factors may also influence this choice. These include the attributes and objects mentioned so far in the dialogue. The mentioned attributes are obviously thought to be important and one would therefore expect them to be given a fairly high salience rating in the active perspective. Thus, the choice of active perspective can be narrowed dow~ to those in which the mentioned attributes appear with high salience.</Paragraph>
      <Paragraph position="3"> By the same token~ the objects mentioned so far in the dialogue can also give a clue concerning the active perspective. One would expect that the active perspective would deem these objects important. Therefore the system might look for perspectives that give high salience ratings to many of the attributes associated with objects that have been mentioned in the discourse.</Paragraph>
      <Paragraph position="4"> In this section I have identified several factors which influence the choice of active perspective. This choice, however, is a question which remains as an open research topic. Still unanswered are questions such as: When does a perspective change? How long is a perspective active? Is there a relationship between a discourse unit \[GS85\] and perspective? Is there any structure to the space of perspectives that would put constraints on moving from one active perspective to another? These questions must be taken up in future research on perspective. null</Paragraph>
    </Section>
    <Section position="5" start_page="102" end_page="103" type="sub_section">
      <SectionTitle>
5.5 An Example
</SectionTitle>
      <Paragraph position="0"> In this section an example is given which indicates how the choice of perspective influences how a misconception may be corrected. Recall that in correcting a misattribution one of the correction schemas used by ROMPER called for a similar object to be offered as a possible object of confusion. A study of transcripts reveals, however, that this schema may be instantiated in different ways depending on the context. Consider the following dialogue: U. I am interested in investing in some securities to use as savings instruments. I want something short-term and I don't have a lot of money to invest so the instrument must have small denominations. I am a bit concerned about the penalties for early withdrawal. What is the penalty on a T-bill? S. Treasury Bills don't have a penalty. Were you thinking of a Money Market Certificate? In this case the money market certificate was seen as being similar to the treasury bill and therefore included in the response. A different object might be used in a different context. Consider: U. I am interested in investing in some securities. Safety is very important to me, so I would probably like to get something from the government. I am a bit concerned about the penalties for early withdrawal. What is the penalty on a T-bill? S. Treasury Bills don't have a penalty. Were you thinking of a Treasury Bond? The difference in these two responses can be explained by different perspectives begin taken on the objects. Suppose that our knowledge base contains the following objects and attributes in the financial securities domain.</Paragraph>
      <Paragraph position="1">  The following perspectives might be reasonable for the domain (here we are assuming salience values from low salience of 0 to high salience of 1):  Notice that the perspective of Savings Instruments highlights' maturity and denominations, and somewhat highlights safety. This indicates that when people are discussing securities as savings instruments, they are most interested in how long their money will be tied up and in what denominations they can save their money. The perspective of Issuing Company, on the other hand, highlights different attributes. When securities are discussed from this perspective, things like who the company is and how stable an investment in the company is, become important. Other attributes of the securities are ignored (recall that attributes not mentioned in the perspective get assigned a low salience rating).</Paragraph>
    </Section>
  </Section>
  <Section position="7" start_page="103" end_page="103" type="metho">
    <SectionTitle>
* I
</SectionTitle>
    <Paragraph position="0"> Consider how perspective might effect the misconception response. Given the discourse preceding the utterance containing the misconception in our first dialogue, it is reasonable to assume that the perspective of &amp;quot;Savings Instruments&amp;quot; is the active perspective at the time of the misconception utterance. 3 A system attempting to respond to this misconception might proceed by attempting to instantiate the wrong object schema described above. Recall that this schema is applicable when there is a similar object which has the property involved in the misconception. The system might collect all objects which have the attribute in question and then test their similarity with the object involved in the misconception. In our knowledge base there are two objects which have the attribute involved in the misconception: Money Market Certificates and T-Bonds.</Paragraph>
    <Paragraph position="1"> Suppose the attributes of these objects were assigned the salience values given by the Savings Instrument perspective.</Paragraph>
    <Paragraph position="2"> Applying the Tversky metric using the salience values attached by this perspective (and assuming a value of 1 for ~,al and fl) we get:</Paragraph>
    <Paragraph position="4"> With these calculations the system would choose the Money Market Certificate as the possible object of confusion and respond: S. Treasury Bills don't have a penalty. Were you thinking of a Money Market Certificate? Contrast the above calculations with calculations that might occur given a different active perspective. The discourse preceding the misconception utterance in the second example suggests the active perspective of &amp;quot;Issuing Company&amp;quot;. Using the salience values attached by this perspective the similarity metric would produce the following calculations:</Paragraph>
    <Paragraph position="6"> in this case a reasonable response by the system would be: S. Treasury Bills don't have a penalty. Were you thinking of a Treasury Bond? As the examples show, changes in the active perspective can account for the same misconception begin responded to in two different ways.</Paragraph>
    <Paragraph position="7"> SROMPER does not calculate the active perspective. Instead, it is input to the system.</Paragraph>
  </Section>
class="xml-element"></Paper>
Download Original XML