File Information

File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/88/j88-2001_metho.xml

Size: 7,993 bytes

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

<?xml version="1.0" standalone="yes"?>
<Paper uid="J88-2001">
  <Title>FOREWORD</Title>
  <Section position="3" start_page="0" end_page="0" type="metho">
    <SectionTitle>
2 REICHENBACH'S TYPOLOGY OF TENSE
</SectionTitle>
    <Paragraph position="0"> Many of the papers collected here build upon Hans Reichenbach's 1947 account of the underlying structure of the English tense system. Reichenbach started from the observation that the collection of English tenses 1 could not be explained either (a) simply in terms of the absolute time of an event or (b) in terms of the relative time of that event to the (purported) time of utterance of the tensed clause. Rather, he proposed that the interpretation of tense requires three separate sensesemantic entities: point of speech (S), point of the event (E), and point of reference (R). 2 The interpretations of S and E are self-evident. R is the time &amp;quot;talked about&amp;quot; or &amp;quot;focused upon&amp;quot; (or, equivalently, the &amp;quot;temporal perspective&amp;quot; from which the described event is viewed). It may be the same as S, as in present perfect (Example  la) or simple present tense (Example lb).</Paragraph>
    <Paragraph position="1"> 1. a. John has climbed Aconcagua and Mt. McKin-</Paragraph>
    <Paragraph position="3"> b. John is in the lounge. (E = R = S) (Here, &amp;quot;&lt;&amp;quot; indicates &amp;quot;temporally prior to&amp;quot;.) It may be the same as E, as in the simple past tense (Example 2a) or simple future tense (Example 2b).</Paragraph>
    <Paragraph position="4"> 2. a. John climbed Aconcagua. (E = R &lt; S) b. John will climb Aconcagua. (S &lt; E = R) It may be in between E and S, as in the past perfect: 3. John had climbed Aconcagua. (E &lt; R &lt; S) or following both E and S (looking back to them), as in the future perfect: 4. John will have climbed Mt. McKinley. (S &lt; E &lt; R) Reichenbach's account is imprecise in some cases, incomplete in some, and only seductively suggestive in others. While all the authors in this volume have taken. Computational Linguistics, Volume 14, Number 2, June 1988 1 Bonnie Webber Foreword Reichenbach's account as their starting point, they differ in what they attempt to flesh out, pin down, or correct, and in the details of how they do so. Nevertheless, there is a remarkable degree of agreement across these accounts. If together they do not yet provide a complete solution to the problem of how we understand and describe events, they may still comprise a new stage from which further progress may be made.</Paragraph>
  </Section>
  <Section position="4" start_page="0" end_page="0" type="metho">
    <SectionTitle>
3 OVERVIEW
</SectionTitle>
    <Paragraph position="0"> There are five papers included in this issue: by Erhard Hinrichs (now at the University of Illinois), by Marc Moens and Mark Steedman (University of Edinburgh), by Sasha Nakhimovsky (Colgate University), by Becky Passoneau (UNISYS) and by myself (University of Pennsylvania). All the papers have gone through extensive revision in response to internal exchange among the authors, in addition to the usual process of external review. Hinrichs describes a meaning-representation language (MRL) for temporal expressions based on higher-order Intensional Logic, that is being used in the JANUS system, a natural-language understanding and generation system under joint development at BBN Laboratories and ISI. He shows how this MRL, which employs temporal indices based on Reichenbach's points of speech, event, and reference, avoids problems that classical tense logics have with even basic temporal adverbials like &amp;quot;yesterday&amp;quot;, with negation, with quantification, and with multiple-clause sentences describing multiple events. He also shows how this MRL permits accurate description of discourse entities evoked by tensed clauses, for use in resolving anaphoric noun phrases (NPs) and other context-sensitive expressions.</Paragraph>
    <Paragraph position="1"> Moens and Steedman propose and argue for a tripartite ontology of events based more on notions of causation and consequence than on purely tempor~d primitives. Their proposal allows a simple solution to what has been called &amp;quot;the imperfective paradox&amp;quot;, to the semantics of &amp;quot;when&amp;quot; clauses, and to the changing sense of an event description as various temporal adverbials are added to it. They also propose Reichenbachian-style analyses for the various &amp;quot;future tenses&amp;quot; in English those constructions used to describe events that are expected, possible, or intended subsequent to speech time. In that, they fill in a gap in Reichenbach's own analysis, which considers only the simple future tense and is equivocal even on that.</Paragraph>
    <Paragraph position="2"> Nakhimovsky describes how our common-sense knowledge of events manifests itself in language and how this knowledge is used in understanding narratives.</Paragraph>
    <Paragraph position="3"> Nakhimovsky discusses three types of common-sense knowledge involved in how we describe events and how, in turn, we understand event descriptions: knowledge of the internal structuring of events, knowledge of their duration and the durations of their various subparts, and knowledge of how events can be viewed.</Paragraph>
    <Paragraph position="4"> (The first and third types of knowledge link with discussions in Moens and Steedman and in Passonneau.) At a practical level, Nakhimovsky shows how such knowledge could be stored in the lexicon.</Paragraph>
    <Paragraph position="5"> Pa,;sonneau describes temporal processing in PUN-DIT, a natural-language text ur~derstanding system developed by researchers at UNISYS. Its purview is clauses that describe actual events such as are frequently found in status reports. In particular, it addresses the problem of processing the distinctive contribufions of those linguistic elements used in describing events of different types. For each clause describing an actual event, Passonneau characterizes the temporal structure of that event and its temporal location vis-hvis speech time or, when relevant, the event described in an adjoining temporal adverbial. Like Moens and Steedman, Passonneau employs a tripartite structure for events in characterizing temporal structure. This paper makes beautifully clear many of the factors involved in correctly characterizing the internal temporal structure of events.</Paragraph>
    <Paragraph position="6"> Finally, I focus on the discourse-related properties of tensed clauses and show that they are very similar to those of anaphoric definite NPs. Specifically, they depend on our knowledge of plausible relations between events (as anaphoric definite NPs depend on our knowledge of plausible relations between entities), and they respond in somewhat similar fashion to a listener's perceptions of discourse structure. In demonstrating the former dependency, I employ a tripartite event structure drawn from the work of Moens and Steedman and from Passonneau. This paper contributes to a long-standing discussion in linguistics as to whether tense should be classified as an anaphor, as well as identifying additional knowledge and mechanisms needed for processing reports and other narrative texts.</Paragraph>
  </Section>
  <Section position="5" start_page="0" end_page="0" type="metho">
    <SectionTitle>
NOTES
</SectionTitle>
    <Paragraph position="0"> 1. geichenbach regarded simple past, present, and future, and past, present, and future perfect as tenses. While others have considered the perfect and the future as belonging to the systems of aspect and modality, rather than tense, Reichenbach's usage remains a convenient shorthand.</Paragraph>
    <Paragraph position="1"> 2. Reichenbach points out in a footnote that Jespersen, more than 20 years before, proposed a related three-point semantics for past perfect and future perfect but did not extend a similar analysis to the other English tenses.</Paragraph>
  </Section>
class="xml-element"></Paper>
Download Original XML