File Information

File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/91/w91-0206_metho.xml

Size: 24,175 bytes

Last Modified: 2025-10-06 14:12:48

<?xml version="1.0" standalone="yes"?>
<Paper uid="W91-0206">
  <Title>Conventional Metaphor and the Lexicon</Title>
  <Section position="5" start_page="56" end_page="56" type="metho">
    <SectionTitle>
2 Constraints from Psycholinguistic Research
</SectionTitle>
    <Paragraph position="0"> While it is difficult to apply results from psycholinguistics to semantic theories in a direct fashion, these results can nevertheless pose useful rough constraints. The results that are of interest here stem from research on the relative difficulty of understanding what has been called literal language versus various kinds of metaphorical, idiomatic, and indirect language \[Gerrig, 1989, Gibbs, 1984, Gibbs, 1989, Ortony et al., 1978\].</Paragraph>
    <Paragraph position="1"> The basic result that will be used is that the time needed to process various kinds of non-literal language does not differ significantly from the time taken to interpret direct language in the appropriate context. Specifically, there is no experimental evidence to indicate that there is a radical difference between the time taken to interpret metaphorical language and that taken to interpret direct literal language. This constraint has been referred to as the total time constraint \[Gerrig, 1989\].</Paragraph>
    <Paragraph position="2"> This rough equivalence of time to process must be taken into account by any realistic approach to semantic interpretation. While the empirical result of equivalent time to process does not necessarily imply that similar mechanisms are at work, in the absence of more fine-grained empirical results indicating that fundamentally different processes are at work, it seems reasonable to assume that the mechanisms will be similar. At the very least it must be shown that if different processes are at work then they should have roughly comparable computational complexity. The next section will show that the proposed methods for metaphor do not meet this criteria.</Paragraph>
  </Section>
  <Section position="6" start_page="56" end_page="57" type="metho">
    <SectionTitle>
3 Problem-Solving Approaches
</SectionTitle>
    <Paragraph position="0"> The major approaches to dealing with the interpretation of non-literal language can all be characterized as &amp;quot;problem-solving&amp;quot; approaches. These include plan-based and analogy-based methods that attempt to find or infer the most likely meaning for a non-literal use when it is encountered \[Carbonell, 1981, DeJong and Waltz, 1983, Fass, 1988, Gentner et al., 1988, Indurkhya, 1987\]. In the case of metaphor, these approaches assert that metaphors arise from an underlying conceptual similarity or analogy between the concepts representing the literal meaning of the words and the concepts underlying the ultimate meaning of the utterance. They make no use of knowledge about the conventions of the language. The task of interpreting metaphoric language is seen as a special purpose problem-solving task requiring access to knowledge and inference techniques that are not otherwise a part of the normal language processing faculties.</Paragraph>
    <Paragraph position="1"> Note that the computational costs of these analogy mechanisms are radically higher than those posed for direct non-metaphorical language. While the details of each approach  differ, they are all fundamentally based on a two stage model where the literal meaning of the sentence is computed and judged to be ill-formed, and then an analogy system is employed to search for an appropriate target meaning. The major problem with these approaches is intractability. The proposed methods are for most practical purposes computationally intractable given any realistic representation of the domain. The problem is particularly acute when the system in intended to be used in some kind of user interface role where response time is critical. Moreover, such methods are directly contradicted by the empirical psycholinguistic evidence described above.</Paragraph>
  </Section>
  <Section position="7" start_page="57" end_page="58" type="metho">
    <SectionTitle>
4 An Emerging View
</SectionTitle>
    <Paragraph position="0"> These psycholinguistic and computational results have led to a surge of computational research in the area of semantic interpretation of non-literal language in recent years. This research has resulted in a number of systems that can handle one or more of the following phenomena: metaphor, metonymy, indirect requests, and somewhat productive phrasal idioms. \[Fass, 1988, Hinkelman, 1989, Martin, 1990, Pustejovsky, 1991, Zernik, 1987\] A careful analysis of these disparate efforts reveals that a common approach to the semantic interpretation of non-literal language may be emerging. At the heart of this approach is a concern with the tension between the conventionality of many non-literal uses, and the ability to understand and generate new uses that go beyond static conventions. This concern has generally led to a two-part approach involving systematic representations that capture conventions, and mechanisms that can dynamically understand and learn new uses as they are encountered.</Paragraph>
    <Paragraph position="1"> The work of Pustejovsky \[Pustejovsky, 1991\] is related in its attempt to reduce the size and complexity of individual lexical entries. The difference is that while the above efforts try to achieve a kind of lexical generativity through the use of extra-lexical and extra-grammatical language conventions, Pustejovsky's work can be seen as attempting to capture this generativity from within a lexicai knowledge base.</Paragraph>
    <Paragraph position="2"> Consider some of the following examples.</Paragraph>
    <Paragraph position="3">  (1) How can I kill a process? (2) My emacs just died.</Paragraph>
    <Paragraph position="4"> (3) Can you open the door? (4) The buses are going on strike.</Paragraph>
    <Paragraph position="5">  Each of these examples makes use of a completely conventional, yet non-literal, way of conveying the intended meaning. The use of the word kill in (1) is consistent with the conventional and productive metaphor that allows computer processes to viewed as livingthings. This productive use also motivates the use of die in (2). Example (3) makes use of a conventional indirect way to make a request in English. In this case, asking about ones ability to perform some task by using Can you, indicates the speakers desire to have that task performed by the hearer. Finally, the last example demonstrates the widespread use of metonymy in English. In this example, the word bus is used to refer to tile distinct, yet obviously related, busdrivers.</Paragraph>
    <Paragraph position="6"> The unifying theme, in all of these examples, is the use of conventional yet productive mechanisms to produce these sentences. The remainder of this paper will introduce a unifying approach to these and similar phenomena that avoids some of the problems inherent in current approaches.</Paragraph>
    <Paragraph position="7">  The following sections provide an analysis that sketches out the nature of this emerging approach. In each of these sections I will first attempt to abstractly characterize the approach and then give a few details of how the approach has been instantiated in the MIDAS \[Martin, 1990\] system. To be specific, Section 5 describes the nature of the knowledge that these systems use, and introduces a new knowledge construct called a Conventional Conceptual Mapping, that abstractly accounts for them all. Section 7 briefly describes how this approach has been applied to metaphor in MIDAS.</Paragraph>
  </Section>
  <Section position="8" start_page="58" end_page="59" type="metho">
    <SectionTitle>
5 Conventional Conceptual Mappings
</SectionTitle>
    <Paragraph position="0"> The fundamental construct that all these systems use is a knowledge structure that allows the system, under certain conditions, to map from one set of concepts to another set of concepts. In the case of MIDAS, these associations are used to represent the source and target concepts of conventional metaphors; in \[Fass, 1988\] they are used to capture the two component parts of metonymies; while in \[Hinkelman, 1989\] they are used to capture knowledge about indirect speech acts. Consider the following examples.</Paragraph>
    <Paragraph position="1">  (5) How can I get out of Emacs? (6) Can you speak Spanish? (7) Plato is on the top shelf.</Paragraph>
    <Paragraph position="2">  In Example (5), MIDAS uses a set of mappings from the domain of enclosures to the domain of computer processes to process this question. In (6), Hinkelman's system may be viewed as making use of structured associations that link features and concepts associated with this surface form, to a concept representing a request to perform the intended meaning. In this example, this association links questions pertaining to the ability to perform an action to requests for that action to be performed. Finally, in (7), Meta5 makes use of mappings that represent conventional metonymies. In this case, the system makes use of a mapping that allows certain kinds of products to be referred to through their producer. In this case, the works of an author can be referred to by referring to the author.</Paragraph>
    <Paragraph position="3"> There are a number of common characteristics that are shared among these efforts. The most important of which is the idea that these associations may be represented at a variety of levels ranging from linguistic features to concepts. This has a number of important ramifications. The first is that it allows these mappings to capture the generalizations at the right level of conceptualization. For example, it is not necessary in (7) to have a new word sense for the word Plato. Rather, the system merely needs to know the fact that Plato was an author to use the proposed metonymic map linking producers to products. It is also important to note that while these conventional associations interact with world knowledge, they can not be conflated with it.</Paragraph>
    <Paragraph position="4"> The second important characteristic shared among these efforts is the idea that these structured associations have explicitly represented constraints on their use. When the constraints on the use of the association call be satisfied in context, then the association can be used to map from one set of concepts to another.</Paragraph>
    <Paragraph position="5"> I call a mapping that has these characteristics a Conventional Conceptual Mapping (CCM). More specifically, a CCM is a structured mapping that has the following characteristics. null  * It can be represented at varying degrees of abstraction.</Paragraph>
    <Paragraph position="6"> * It can have constraints on its use explicitly represented.</Paragraph>
    <Paragraph position="7">  Not surprisingly, none of the systems mentioned above fits this description precisely. Most deal with only one of the phenomena, while ignoring the others. For example, Hinkelman's system deals only with speech act level conventions, while Martin's MIDAS system deals only with conventional metaphors. While Fass's META5 system does handle metaphor and metonymy, only metonymy is handled in a way that uses ccM's.</Paragraph>
    <Paragraph position="8"> The following section will give a high level discussion of how the this approach can be applied to the problem of metaphor. Section 77 will then detail the current state of an implementation of this approach.</Paragraph>
  </Section>
  <Section position="9" start_page="59" end_page="60" type="metho">
    <SectionTitle>
6 A Sample Metaphor Analysis
</SectionTitle>
    <Paragraph position="0"> To make this discussion more concrete, consider some of these issues in terms of the following examples.</Paragraph>
    <Paragraph position="1">  came to the conclusion that Mike was right. reached the conclusion that Mike was right. I arrived at the conclusion that Mike was right. I was led to the conclusion that Mike was right. I was dragged kicking and screaming to the conclusion that Mike was right. That Mike was right came to me.</Paragraph>
    <Paragraph position="2"> It came to me that Mike was right.</Paragraph>
    <Paragraph position="3"> It hit me that Mike was right.</Paragraph>
    <Paragraph position="4"> It struck me that Mike was right.</Paragraph>
    <Paragraph position="5"> Mike struck me as being right.</Paragraph>
    <Paragraph position="6"> Mike came across as being right.</Paragraph>
    <Paragraph position="7"> Each of these examples expresses the idea that someone is changing state with respect to some belief. More specifically, they express the idea that the believer now believes some proposition that had not been previously held. They all express this notion through the use of a spatial metaphor that has the following entailments: beliefs are external objects with locations, believers have locations, shared location between a believer and a proposition indicates belief, and finally movement to a shared location indicates a state-change resulting in belief. \[Barnden, 1989\] Given this general metaphor, we can narrow the discussion further by isolating on the behavior of a single lexical item.</Paragraph>
    <Paragraph position="8">  (19) The idea that Mike was smart came to me.</Paragraph>
    <Paragraph position="9"> (20) It came to me that Mike was smart.</Paragraph>
    <Paragraph position="10"> (21) I came to the conclusion that Mike was smart.</Paragraph>
    <Paragraph position="11"> (22) ?I came to the idea that Mike was smart.</Paragraph>
    <Paragraph position="12"> (23) I came upon the idea that Mike was smart.</Paragraph>
    <Paragraph position="13">  These examples illustrate at least two broad semantic senses and four different syntactic environments for the word come. This leads to the big question:  Do these meanings, and these syntactic environments, have to be listed in the lexical entry for come, or can these facts be motivated by other independent language conventions?~ The following discussion will raise a series of more specific issues surrounding this question and provide some flavor of the research program we are pursuing. Consider first the two broad senses that are evident here. In the first sense, the new proposition is the mover, changing its location to the location of the believer. One implication of this sense is that the believer did not consciously expend any effort to produce this belief. This sense is illustrated in (19) and (20). Examples (21) through (23) illustrate the second sense that has the believer actively moving to the new proposition. This sense has more of an implication that the believer is taking an active part in the process.</Paragraph>
    <Paragraph position="14"> We are currently investigating the proposition that these two senses result from the interaction of a single broad spatial metaphor, the core spatial semantics of the word come, and facts about the situation. It is, therefore, not necessary to have either two lexical senses or two conventional metaphors.</Paragraph>
    <Paragraph position="15"> Now consider the syntactic variation exhibited in examples (19) and (20). In both of these examples the proposition is in motion. In (19) it appears in the subject position, while in (20) it is extraposed. Our current hypothesis is that it is not necessary to list in the lexical entry for come the fact that it permits extraposition. Rather this flows from the general requirements of the extraposition construction combined with the semantics of target concept of this metaphor.</Paragraph>
    <Paragraph position="16"> Next consider the apparent well-formedness variation between (21) and (22). The use of come to with conclusion is clearly preferred. Again the metaphorically focussed approach advocated here would say that the metaphorical semantics of the word conclusion lead it to naturally fit into the spatial metaphor governing the use of come. Finally, consider the difference between example (23) and (21). This example seems to imply that, while the believer was in motion towards the proposition, the discovery was in fact something of a chance occurrence. But of course, this would also be implied by a literal use of come upon. Therefore, this difference is attributable to a difference in the spatial semantics of come. The question remains as to whether it is necessary to list this fact in the lexical entry for come.</Paragraph>
  </Section>
  <Section position="10" start_page="60" end_page="62" type="metho">
    <SectionTitle>
7 Overview of MIDAS
</SectionTitle>
    <Paragraph position="0"> This section provides a brief overview of our current computational realization of this approach to metaphor. In particular, it introduces the following issues.</Paragraph>
    <Paragraph position="1"> Representation: The explicit representation of the conventional metaphors in a language in the form of explicit associations between concepts.</Paragraph>
    <Paragraph position="2"> Interpretation: The correct and efficient application of this metaphoric knowledge to the interpretation of metaphoric language.</Paragraph>
    <Paragraph position="3"> Under this view, the proper way to approach the study of metaphor is to study the underlying details of individual metaphors and systems of metaphors in the language. This approach follows on the metaphor work of Lakoff and Johnson \[Lakoff and Johnson, 1980\] and the computational approaches to metaphor described in \[Jacobs, 1985, Norvig, 1987\].</Paragraph>
    <Paragraph position="4">  This approach has been embodied in MIDAS (Metaphor Interpretation, Denotation, and Acquisition System) \[Martin, 1990\] MIDAS is a set of computer programs that can be used to perform the following tasks: explicitly represent knowledge about conventional metaphors, apply this knowledge to interpret metaphoric language, and learn new metaphors as they are encountered.</Paragraph>
    <Section position="1" start_page="61" end_page="62" type="sub_section">
      <SectionTitle>
7.1 Knowledge Representation
</SectionTitle>
      <Paragraph position="0"> Consider the following simple example of a conventional UNIX metaphor. The metaphorical use of the word in reflects a systematic metaphorical structuring of computer processes as enclosures.</Paragraph>
      <Paragraph position="1"> (24) I am in Emacs.</Paragraph>
      <Paragraph position="2"> Metaphors like this may be said to consist of the following component concepts: a source component, a target component, and a set of conventional associations from the source to target. The target consists of tile concepts to which the words are actually referring. The source refers to the concepts in terms of which the intended target concepts are being viewed. In this example, the target concepts are those representing the state of currently using a computer process. The source concepts are those that involve the state of being contained within some enclosure.</Paragraph>
      <Paragraph position="3"> The approach taken here is to explicitly represent conventional metaphors as sets of associations between source and target concepts. The metaphor specifies how the source concepts reflected in the surface language correspond to various target concepts. In this case, the metaphor consists of component associations that specify that the state of being enclosed represents the idea of currently using the editor, where the user plays the role of the enclosed thing, and the Emacs process plays the role of the enclosure. These associations also serve to delimit the particular parts of the various source and target domains that are relevant to particular conventional metaphors.</Paragraph>
      <Paragraph position="4"> Note also that these source-target associations are represented at the conceptual and not the lexical level. Any single lexical item or expression that can be construed as referring to the source concept of a known metaphor, may invoke that metaphor. In this example, the source component of the metaphor is attached to the concept of being enclosed, not to the lexical item in.</Paragraph>
      <Paragraph position="5"> These sets of metaphoric associations, along with the concepts that comprise the source and target domains, are represented using the KODIAK \[Wilensky, 1986\] representation language. KODIAK is an extended semantic network language in the tradition of KL-ONE \[Brachman and Schmolze, 1985\] and its variants.</Paragraph>
      <Paragraph position="6"> These sets of metaphoric associations representing conventional metaphors are full-fledged KODIAK concepts. As such, they can be related to other concepts and arranged in abstraction hierarchies using the inheritance mechanisms provided by KODIAK. The hierarchical organization of conventional metaphoric knowledge is the primary means used to capture the regularities exhibited by the system of metaphors in the language. Specifically, KODIAK is used to represent specialized domain specific metaphors, pervasive high-level metaphors, and the systems of relations among related metaphors.</Paragraph>
    </Section>
    <Section position="2" start_page="62" end_page="62" type="sub_section">
      <SectionTitle>
7.2 Interpretation
</SectionTitle>
      <Paragraph position="0"> The interpretation process in MIDAS is basically one that views a given input sentence as providing a set of constraints on possible interpretations. MIDAS checks the input constraints against all the possible interpretations that can be conventionally associated with the input. Interpretations that are coherent with the constraints are returned. The possible conventional interpretations may include direct non-metaphoric interpretations, as well as all the conventional metaphors that are invoked by the input.</Paragraph>
      <Paragraph position="1"> Consider the details of the following shortened trace. In this example, MIDAS must find a coherent interpretation for this use of enter. MIDAS finds, and attempts to apply, all the conventional metaphorical and non-metaphorical concepts associated directly with, or inherited by, this concept. In this case, it finds that the only conventional interpretation that is consistent with the input is the one that results from the application of the known</Paragraph>
      <Paragraph position="3"> A parser first produces a syntactic analysis and a preliminary semantic representation of the input. At this point in the analysis, uc calls upon MIDAS to begin a deeper analysis of this initial representation.</Paragraph>
      <Paragraph position="4"> Failed interpretation: Entering50 as Entering.</Paragraph>
      <Paragraph position="5"> Failed interpretation: EnteringSO as Enter-Association.</Paragraph>
      <Paragraph position="6"> Valid known metaphorical interpretation: EnteringSO as Enter-Lisp.</Paragraph>
      <Paragraph position="7"> The case structure of this preliminary representation is checked against the semantic constraints of all the interpretations conventionally associated with the Entering concept. In this case, MIDAS finds that the direct interpretation and one of the other possible entering metaphors can be rejected before the appropriate Enter-Lisp metaphor is found. It is important to realize that the order of tile search performed here is arbitrary. MIDAS is exhaustively finding all conventional interpretations that are consistent with the input. The determination of consistency for any given interpretation is independent of the consistency of any of the other possible interpretations. In particular, the well-formedness of a direct, or literal, interpretation has no effect on whether or not a metaphorical interpretation will be found. It follows from this that the order of the search through the possible interpretations has no effect on which interpretations will ultimately be produced.  MIDAS then begins the process of mapping from the given source concepts to the appropriate target concepts based on the constraints imposed by the metaphor. The mapping process, called metaphoric unviewing, creates a new instance of the metaphor itself along with the attendant source and target concepts. In this example, the source concept of Entering is mapped to the target concept Invoke-Lisp as specified by the metaphor.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>
Download Original XML