| { |
| "paper_id": "P82-1014", |
| "header": { |
| "generated_with": "S2ORC 1.0.0", |
| "date_generated": "2023-01-19T09:16:24.499240Z" |
| }, |
| "title": "PROCESSING ENGLISH WITH A GENERALIZED PHRASE STRUCTURE GRAMMAR", |
| "authors": [ |
| { |
| "first": "Jean", |
| "middle": [ |
| "Mark" |
| ], |
| "last": "Gawron", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Jonathan", |
| "middle": [], |
| "last": "King", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "John", |
| "middle": [], |
| "last": "Lamping", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Egon", |
| "middle": [], |
| "last": "Loebner", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Anne", |
| "middle": [], |
| "last": "Paulson", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Geoffrey", |
| "middle": [ |
| "K" |
| ], |
| "last": "Pullum", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Ivan", |
| "middle": [ |
| "A" |
| ], |
| "last": "Sag", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| }, |
| { |
| "first": "Thomas", |
| "middle": [], |
| "last": "Wasow", |
| "suffix": "", |
| "affiliation": { |
| "laboratory": "", |
| "institution": "Computer Research Center Hewlett Packard Company", |
| "location": { |
| "addrLine": "1501 Page Mill Road", |
| "postCode": "94304", |
| "settlement": "Palo Alto", |
| "region": "CA" |
| } |
| }, |
| "email": "" |
| } |
| ], |
| "year": "", |
| "venue": null, |
| "identifiers": {}, |
| "abstract": "", |
| "pdf_parse": { |
| "paper_id": "P82-1014", |
| "_pdf_hash": "", |
| "abstract": [], |
| "body_text": [ |
| { |
| "text": "This paper is an interim progress report on linguistic research carried out at Hewlett-Packard Laboratories since the summer of 1981.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "The research had three goals: (1) demonstrating the computational tractability of Generalized Phrase Structure Grammar (GPSG), (2) implementing a GPSG system covering a large fragment of English, and (3) establishing the feasibility of using GPSG for interactions with an inferencing knowledge base.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Section 2 describes the general architecture of the system. Section 3 discusses the grammar and the lexicon.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "A brief dicussion of the parsing technique used in found in Section 4.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Section 5 discusses the semantics of the system, and Section 6 presents ~ detailed example of a parse-tree complete with semantics.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Some typical examples that the system can handle are given in the Appendix.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "The system is based on recent developments in syntax and semantics, reflecting a modular view in which grammatical structure an~ abstract logical structure have independent status. The understanding of a sentence occurs in a number of stages, distinct from each other and governed by different principles of organization. We are opposed to the idea that language understanding can be achieved without detailed syntactic analysis.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "There is, of course, a massive pragmatic component to human linguistic interaction.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "But we hold that pragmatic inference makes use of a logically prior grammatical and semantic analysis. This can be fruitfully modeled and exploited even in the complete absence of any modeling of pragmatic inferencing capability. However, this does not entail an incompatibility between our work and research on modeling discourse organization and conversational interaction directly=", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Ultimately, a successful language understanding system wilt require both kinds of research, combining the advantages of precise, grammar-driven analysis of utterance structure and pragmatic inferencing based on discourse structures and knowledge of the world. We stress, however, that our concerns at this stage do not extend beyond the specification of a system that can efficiently extract literal meaning from isolated sentences of arbitrarily complex grammatical structure.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Future systems will exploit the literal meaning thus extracted in more ambitious applications that involve pragmatic reasoning and discourse manipulation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "The system embodies two features that simultaneously promote extensibility, facilitate modification, and increase efficiency. The first is that its grammar is context-free in the informal sense sometimes (rather misleadingly) used in discussions of the autonomy of grammar and pragmatics:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "the syntactic rules and the semantic translation rules are independent of the specific application domain. Our rules are not devised ad hoc with a particular application or type of interaction in mind.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "Instead, they are motivated by recent theoretical developments in natural language syntax, and evaluated by the usual linguistic canons of simplicity and generality. No changes in the knowledge base or other exigencies deriving from a particular context of application can introduce a problem for the grammar (as distinct, of course, from the lexicon).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "The second relevant feature is that the grammar ir the-system is context-free in the sense of formal language theory. This makes the extensive mathematical literature on context-free phrase structure grammars (CF-PSG's) directly relevant to the enterprise, and permits utilization of all the well-known techniques for the computational implementation of context-free grammars.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "It might seem anachronistic to base a language understanding system on context-free parsing.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "As Pratt (1975, 423) observes: \"It is fashionable these days to want to avoid all reference to context-free grammars beyond warning students that they are unfit for computer consumption as far as computational linguistics is concerned.\" Moreover, widely accepted arguments have been given in the linguistics literature to the effect that some human languages are not even weakly context-free and thus cannot possibly be described by a CF-PSG.", |
| "cite_spans": [ |
| { |
| "start": 3, |
| "end": 20, |
| "text": "Pratt (1975, 423)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "However, Gazdar and Pullum (1982) answer all of these arguments, showing that they are either formally invalid or empirically unsupported or both. It seems appropriate, therefore, to take a renewed interest in the possibility of CF-PSG description of human languages, both in computational linguistics and in linguistic research generally.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "INTRODUCTION", |
| "sec_num": null |
| }, |
| { |
| "text": "The linguistic basis of the GPSG linguistic system resides in the work reported in Gazdar (1981, 1982) and Gazdar, Pullum, and Sag (1981) . 1 These papers argue on empirical and theoretical grounds that context-freeness is a desirable constraint on grammars.", |
| "cite_spans": [ |
| { |
| "start": 90, |
| "end": 96, |
| "text": "(1981,", |
| "ref_id": "BIBREF10" |
| }, |
| { |
| "start": 97, |
| "end": 102, |
| "text": "1982)", |
| "ref_id": null |
| }, |
| { |
| "start": 131, |
| "end": 137, |
| "text": "(1981)", |
| "ref_id": "BIBREF10" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "It clearly would not be so desirable, however, if (1) it led to lost generalizations or (2) it resulted in an unmanageable number of rules in the grammar. Gazdar (1982) proposes a way of simultaneously avoiding these two problems. Linguistic generalizations can be captured in a context-free grammar with a metagrammor, i.e. a higher-level grammar that generates the actual grammar as its language.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "The metagrammar has two kinds of statements:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "(1) Rule schemata. These are basically like ordinary rules, except that they contain variables ranging over categories and features.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "(2) Metarules.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "These are implicational statements, written in the form ===>B, which capture relations between rules.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "A metarule ===>t~ is interpreted as saying, \"for every rule that is an instantiation of the schema =, there is a corresponding rule of form [5. \" Here 13 will be @(~), where 8 issome mapping specified partly by the general theory of grammar and partly in the metarule formulation.", |
| "cite_spans": [ |
| { |
| "start": 140, |
| "end": 143, |
| "text": "[5.", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "For instance, it is taken to be part of the theory of grammar that @ preserves unchanged the subcategorization (rule name) features of rules (cf. below). In our terms the latter is information linking lexical items of a particular category to specific environments in which that category is introduced by phrase structure rules.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 111, |
| "end": 122, |
| "text": "(rule name)", |
| "ref_id": null |
| } |
| ], |
| "eq_spans": [], |
| "section": "COMPONENTS OF THE SYSTEM", |
| "sec_num": "2." |
| }, |
| { |
| "text": "Presence in the lexical entry for an item I of the feature R (where R is the name of a rule) indicates that / may appear in structures admitted by R, and absence indicates that it may not.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "The semantic information in a lexical entry is sometimes simple, directly linking a lexical item with some HIRE predicate or relation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "With verbs or prepositions, there is also a specification of what case roles to associate with particular arguments (cf. below for discussion of case roles). Expressions that make a complex logical contribution to the sentence in which they appear witl in general have complicated translations. Thus every has the translation-2. There is a theoretical issue here about whether semantic translation rules need to be stipulated for each syntactic rule or whether there is a general way of predicting their form. See Klein and Sag (t981) for an attempt to develop the latter view, which is not at present implemented in our system.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "(LAMBDA P (LAMBDA Q ((FORALL X (P X)) --> (Q x)))),", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "This indicates that it denotes a function which takes as argument a set P, and returns the set of properties that are true of all members of that set (cf. below for slightly more detailed discussion).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "A typical rule looks like this:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "<VPI09: V] -> V N]! N!I2: ((V N!!2) N!!)>", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "The exclamation marks here are our notation for the bars in an X-bar category system.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "(See Jackendoff (1977) for a theory of this type--though one which differs on points of detail from ours.)", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "The rule has the form <a: b: c>. Here a is the name 'VP109'; b is a condition that will admit a node labeled 'V!' if it has three daughter nodes labeled respectively 'V' (verb), 'Nit' (noun phrase at the second bar level), and 'NI!' (the numeral 2 being merely an index to permit reference to a specific symbol in the semantics, the metarules, and the rule compiler, and is not a part of the category label);", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "and c is a semantic translation rule stating that the V constituent translates as a function expression taking as its argument the translation of the second N!!, the result being a function expression to be applied to the translation of the first N!!.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "The", |
| "sec_num": null |
| }, |
| { |
| "text": "the rule name is one of the feature values marked on the lexical head of any rule that introduces a lexical category (as this one introduces V).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "Only verbs marked with that feature value satisfy this rule. For example, if we include in the lexicon the word give and assign to it the feature VPI09, then this rule would generate the verb phrase gave Anne a job.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "A typical metarule is the passive metarule, which looks like this (ignoring semantics):", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "<PAS: <V! -> V NI! W > => <V! -> V[PAS] W>>", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "W is a string variable ranging over zero or more category symbols. The metarule has the form <N: <A> => <B>>, where N is a name and <A> and <B > are schemata that have rules as their instantiations when appropriate substitutions are made for the free variables.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "This metarule says that for every rule that expands a verb phrase as verb followed by noun phrase followed by anything else (including nothing else), there is another rule that expands verb phrase as verb with passive morphology followed by whatever followed the noun phrase in the given rule. The metarule PAS would apply to grammar rule VP109 given above, yielding the rule:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "<VP109: V! -> V[PAS] N{!>", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "As we noted above, the rule number feature is preserved here, so we get Anne was given a job, where the passive verb phrase is given a job, but not *Anne was hired a job. 3", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "Passive sentences are thus analyzed directly, and not reduced to the form of active sentences in the course of being analyzed, in the way that is familiar from work on transformational grammars and on ATN's.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "However, this does not mean that no relation between passives and their active counterparts is expressed in the system, because the rules for analyzing passives are in a sense derivatively defined on the basis of' rules for analyzing actives.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "More difficult than treating passives and the like, and often cited as literally impossible within a context-free grammar',\" is treating constructions like questions and relative clauses.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "The apparent difficulty resides in the fact that in a question like The problem is thus one of guaranteeing a grammatical dependency across a context that may be arbitrarily wide, while keeping the grammar context-free. The technique used is introduced into the linguistic literature by Gazdar (1981) .", |
| "cite_spans": [ |
| { |
| "start": 294, |
| "end": 300, |
| "text": "(1981)", |
| "ref_id": "BIBREF10" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "It involves an augmentation of the nonterminal vocabulary of the grammar that permits constituents with \"gaps\" to be treated as not belonging to the same category as similar constituents without gaps.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "This would be an unwelcome and inelegant enlargement of the grammar if it had to be done by means of case-by-case stipulation, but again the use of a metagrammar avoids this.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "Gazdar (1981) and therefore defines rules that allow for actual gaps--i.e., missing constituents. In this way, complete sets of rules for describing the unbounded dependencies found in interrogative and relative clauses can readily be written.", |
| "cite_spans": [ |
| { |
| "start": 7, |
| "end": 13, |
| "text": "(1981)", |
| "ref_id": "BIBREF10" |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "Even long-distance agreement facts can be (and are) captured, since the morphosyntactic features relevant to a specific case of agreement are present in the feature composition of any given ~'.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "By a general convention in the theory of grammar,", |
| "sec_num": null |
| }, |
| { |
| "text": "The system is initialized by expanding out the grammar. That is, tile metarules are applied to the rules to produce the full rule set, which is then compiled and used by the parser.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "Metarules are not consulted during the process of parsing. One might well wonder about the possible benefits of the other alternative: a parser that made the metarule-derived rules to order each time they were needed, instead of consulting a precompiled list.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "This possibility has been explored by Kay (1982).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "Kay draws an analogy between metarules and phonological rules, modeling both by means of finite state transducers.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "We believe that this line is worth pursuing;", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "however, the GPSG system currently operates off a precompiled set of rules.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "Application of ten metarules to forty basic rules yielded 283 grammar rules in the 1/1/82 version of the GPSG system.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "Since then the grammar has been expanded somewhat, though the current version is still undergoing some debugging, and the number of rules is unstable. The size of the grammar-plus-metarules system grows by a factor of five or six through the rule compilation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "The great practical advantage of using a metarule-induced grammar is, therefore, that the work of designing and revising the system of linguistic rules can proceed on a body of statements that is under twenty percent of the size it would be if it were formulated as a simple list of context-free rules.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "The system uses a standard type of top-down parser with no Iookahead, augmented slightly to prevent it from looking for a given constituent starting in a given spot more than once.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "It produces, in parallel, all legal parse trees for a sentence, with semantic translations associated with each node.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "PARSING", |
| "sec_num": "4." |
| }, |
| { |
| "text": "The semantics handler uses the translation rule associated with a node to construct its semantics from the semantics of its daughters. This construction makes crucial use of a procedure that we call Cooper storage (after Robin Cooper; see below).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "In the spirit of current research in formal semantics, each syntactic constituent is associated directly with a single logic expression (modulo Cooper Storage), rather than any program or procedure for producing such an expression. Our semantic analysis thus embraces the principle of \"surface compositionality.\" The semantic representations derived at each node are referred to as the Logical Representation (LR).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The disambiguator provides the crucial transition from LR to HIRoE queries; the disambiguator uses information about the sort, or domoin of definition, of various terms in the logical representation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "One of the most important functions of the disambiguator is to eliminate parses that do not make sense in the conceptual scheme of HIRE.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "HIRE is a relational database with a certain amount of inferencin9 capability.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "It is implemented in SPHERE, a database system which is a descendant of FOL (described in Weyhrauch (1980)).", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Many of the relation-names output by the disambiguator are derived relations defined by axioms in SPHERE.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The SPHERE environment was important for this application, since it was essential to have something that could process first-order logical output, and SPHERE does just that.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "A noticeable recent trend in database theory has been a move toward an interdisciplinary comingling of mathematical logic and relational database technology (see especially Gallaire and Minker (1978) and Gallaire, Minker and Nicolas (198])).", |
| "cite_spans": [ |
| { |
| "start": 173, |
| "end": 199, |
| "text": "Gallaire and Minker (1978)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "We regard it as an important fact about the GPSG system that links computational linguistics to first-order logical representation just as the work referred to above has linked first-order logic to relational database theory. We believe that SPHERE offers promising prospects for a knowledge representation system that is principled and general in the way that we have tried to exemplify in our syntactic and semantic rule system.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Filman, Lamping and Montalvo (]982) present details of some capabilities of SPHERE that we have not as yet exploited in our work, involving the use of multiple contexts to represent viewpoints, beliefs, and modalities, which are generally regarded as insuperable stumbling-blocks to first-order logic approaches.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Thus far the linguistic work we have described has been in keeping with GPSG presented in the papers cited above. However two semantic innovations have been introduced to facilitate the disambiguator's translation from LR to a HIRE query.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "As a result the linguistic system version of LR has two new properties:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "(1) The intensional logic of the published work was set aside and LR was designed to be an extensional first-order language. Although constituent translations built up on the way to a root node may be second-order, the systemmaintains first-order reducibility. This reducibility is illustrated by the following analysis of noun phrases as second-order properties (essentially the analysis of Montague (]970)). For example, the proper name Egon and the quantified noun phrase every opplicant are both translated as sets of properties: Egon = LAMBDA P (P EGON) Every applicant = LAMBDA P (FORALL X ((APPLICANT X) --> (P X)))", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Egon is translated as the set of properties true of Egon, and every applicant, as the set of properties true of all applicants.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Since basic predicates in the logic are first-order, neither of the above expressions can be made the direct \u2022 argument of any basic predicate;", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "instead the argument is some unique entity-level variable which is later bound to the quantifier-expression by quantifying in.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "This technique is essentially the storage device proposed in Cooper (1975) . One advantage of this method of \"deferring\" the introduction into the interpretation process of phrases with quantifier meanings is that it allows for a natural, nonsyntactic treatment of scope ambiguities. Another is that with a logic limited to first-order predicates, there is still a natural treatment for coordinated noun phrases of apparently heterogeneous semantics, such as Egon and every applicant.", |
| "cite_spans": [ |
| { |
| "start": 61, |
| "end": 74, |
| "text": "Cooper (1975)", |
| "ref_id": null |
| } |
| ], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "(2) HIRE represents events as objects. I n order to accomodate this many-to-many mapping between a verb and particular relations in a knowledge base, the lexicon stipulates special relations that link a verb to its eventual arguments.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Following Fillmore (1968), these mediating relations are called case roles.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The disambiguator narrows the case roles down to specific knowledge base relations.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "To take a simple example, Anne works for HP has a logical representation reducible to:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "(EXISTS SIGMA (AND (EMPLOYMENT SIGMA) (AG SIGMA ANNE) (LOC SIGMA HP)))", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Here SIGMA is a variable over situations or event instantiations, s The formula may be read, \"There is an employment-situation whose Agent is Anne and whose Location is HP.\" The lexical entry for work supplies the information that its subject is an Agent and its complement a Location. The disambiguator now needs to further specify the case roles as HIRE relations.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "It does this by treating each atomic formula in the expression locally, using the fact that Anne is a person in order to interpret AG, and the fact that HP is an organization in order to interpret LOC. In this case, it interprets the AG role as employment.employee and the LOC role as employment.organization.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The advantages of using the roles in Logical Representation, rather than going directly to predicates in a knowledge base, include (1) the ability to interpret at least some prepositional phrases, those known as adjuncts, without subcategorizing verbs specially for them, since the case role may be supplied either by a verb or a preposition.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "(2) the option of interpreting 'vague' verbs such as have and give using case roles without event types. These verbs, then, become \"purely\" relational. representations, and to make all knowledge base-specific predicates and relations the exclusive province of the disambiguator.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "One important means to that end is case roles, which allow us a level of abstract, purely \"linguistic\" relations to mediate between logical representations and HIRE queries.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Another is the use of general event types such as labor, to replace event-types specific to HIRE, such as employments.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The case roles maintain a separation between the domain representation language and LR. Insofar as that separation is achieved, then absolute portability of the system, up to and including the lexicon, is an attainable goal.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Absolute portability obviously has immediate practical benefits for any system that expects to handle a large fragment of English, since the effort in moving from one application to another will be limited to \"tuning\" the disambiguator to a new ontology, and adding \"specialized\" vocabulary. The actual rules governing the production of first-order logical representations make no reference to the facts of HIRE.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The question remains of just how portable the current lexicon is; the answer is that much of it is already domain independent. Quantifiers like every (as we saw in the discussion of NP semantics) are expressed as logical constants;", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "verbs like give are expressed entirely in terms of the case relations that hold among their arguments.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "Verbs like work can be abstracted away from the domain by a simple extension.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "The obvious goal is to try to give domain independent representations to a core vocabulary of English that could be used in a variety of application domains.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SEMANTICS", |
| "sec_num": "5." |
| }, |
| { |
| "text": "We shall now give a slightly more detailed illustration of how the syntax and compositional semantics rules work.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "We are still simplifying considerably, since we have selected an example where rote frames are not involved, and we are not employing features on nodes.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "Here we have the grammar of a trivial subset of English: The syntax of a lexical entry is <L: C: T>, where L is the spelling of the item, C is its grammatical category and feature specification (if other than the default set) and T is its translation into LR.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "Consider how we assign an LR to a sentence like Every applicant is competent. The translation of every supplies most of the structure of the universal quantification needed in LR. It represents a function from properties to functions from properties to truth values, so when applied to applicant it yields a constituent, namely every applicant, which has one of the property slots filled, and represents a function from properties to truth-values; it is:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "(LAMBDA P (FORALL X ((APPLICANT X) IMPLIES (P X))))", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "This function can now be applied to the function denoted by competent, i.e.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "AN EXAMPLE", |
| "sec_num": "6." |
| }, |
| { |
| "text": "This yields:", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "(FORALL X ((APPLICANT X) IMPLIES (LAMBDA Y (EXPERT.LEVEL HIGH Y)) X))", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "And after one more lambda-conversion, we have: 1 shows one parse tree that would be generated by the above rules, together with its logical translation. The sentence is Bill interviewed every applicant.", |
| "cite_spans": [], |
| "ref_spans": [ |
| { |
| "start": 47, |
| "end": 48, |
| "text": "1", |
| "ref_id": "FIGREF3" |
| } |
| ], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "( FORALL X ((APPLICANT X) IMPLIES (EXPERT.LEVEL HIGH X))) Fig.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "The complicated translation of the VP is necessary because INTERVIEW is a one-place predicate that takes an entity-type argument, not the type of function that every applicant denotes.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "We thus defer combining the NP translation with the verb by using Cooper storage. A translation with a stored NP is represented above in angle-brackets. Notice that at the S node the NP every applicant is still stored, but the subject is not stored.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "It has directly combined with the VP, by taking the VP as an argument.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "INTERVIEW is itself a two-place predicate, but one of its argument places has been filled by a place-holding variable, X1.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "There is th~Js ~ only one slot left.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "The translation can now be completed via the operations of Storage Retrieval and lambda conversion. First, we simplify the part of the semantics that isn't in storage: The function (LAMBDA P (P BILL)) has been evaluated with P set to the value (INTERVIEW X1); this is a. conventional lambda-conversion. The rule for storage retrieval is to make a one-place predicate of the sentence translation by lambda-binding the placeholding variable, and then to apply the NP translation as a function to the result. The S-node translation above becomes: This is the desired final result.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "( LAMBDA Y (EXPERT.LEVEL HIGH Y))", |
| "sec_num": null |
| }, |
| { |
| "text": "What we have outlined is a natural language system that is a direct implementation of a linguistic theory.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CONCLUSION", |
| "sec_num": "7." |
| }, |
| { |
| "text": "We have argued that in this case the linguistic theory has the special appeal of computational tractability (promoted by its context-freeness), and that the system as a whole offers the hope of a happy marriage of linguistic theory, mathematical logic, and advanced computer applications.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CONCLUSION", |
| "sec_num": "7." |
| }, |
| { |
| "text": "The system's theoretical underpinnings give it compatibility with current research in Generalized Phrase Structure Grammar, and its augmented first order logic gives it compatibility with a whole body of ongoing research in the field of model-theoretic semantics.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CONCLUSION", |
| "sec_num": "7." |
| }, |
| { |
| "text": "The work done thus far is only the first step on the road to a robust and practical natural language processor, but the guiding principle throughout has been extensibility, both of the grammar, and of the applicability to various spheres of computation.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "CONCLUSION", |
| "sec_num": "7." |
| }, |
| { |
| "text": "Grateful acknowledgement is given to two brave souls, Steve Gadol and Bob Kanefsky, who helped give this system some of its credibility by implementing the actual hook-up with HIRE. Thanks are also due Robert Filman and Bert Raphael for helpful comments on an early version of this paper.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "ACKNOWLEDGEMENT", |
| "sec_num": null |
| }, |
| { |
| "text": "And a special thanks is due Richard Weyhrauch, for encouragement, wise advice, and comfort in times of debugging.", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "ACKNOWLEDGEMENT", |
| "sec_num": null |
| } |
| ], |
| "back_matter": [ |
| { |
| "text": "This appendix lists some sentences that are actually translated into HIRE and answered by the current system. Declarative sentences presented to the system are evaluated with respect with their truth value in the usual way, and thus also function as queries. ", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "APPENDIX", |
| "sec_num": null |
| }, |
| { |
| "text": "Cooper", |
| "cite_spans": [], |
| "ref_spans": [], |
| "eq_spans": [], |
| "section": "SIMPLE SENTENCES", |
| "sec_num": null |
| } |
| ], |
| "bib_entries": { |
| "BIBREF1": { |
| "ref_id": "b1", |
| "title": "Egon works for HP", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Egon works for HP.", |
| "links": null |
| }, |
| "BIBREF2": { |
| "ref_id": "b2", |
| "title": "HP offered Montague the position", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "HP offered Montague the position.", |
| "links": null |
| }, |
| "BIBREF3": { |
| "ref_id": "b3", |
| "title": "HP gave Montague a job", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "HP gave Montague a job.", |
| "links": null |
| }, |
| "BIBREF4": { |
| "ref_id": "b4", |
| "title": "Montague got a job from HP", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Montague got a job from HP.", |
| "links": null |
| }, |
| "BIBREF5": { |
| "ref_id": "b5", |
| "title": "Montague's job is at HP", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Montague's job is at HP", |
| "links": null |
| }, |
| "BIBREF6": { |
| "ref_id": "b6", |
| "title": "HP's offer was to Capulet", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "HP's offer was to Capulet.", |
| "links": null |
| }, |
| "BIBREF7": { |
| "ref_id": "b7", |
| "title": "Montague had a meeting with Capulet", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Montague had a meeting with Capulet.", |
| "links": null |
| }, |
| "BIBREF8": { |
| "ref_id": "b8", |
| "title": "Capulet has an offer from Xerox. 10. Capulet is competent. IMPERATIVES AND QUESTIONS 11. Find the programmers in CRC who attended the meeting", |
| "authors": [], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "Capulet has an offer from Xerox. 10. Capulet is competent. IMPERATIVES AND QUESTIONS 11. Find the programmers in CRC who attended the meeting.", |
| "links": null |
| }, |
| "BIBREF9": { |
| "ref_id": "b9", |
| "title": "Which manager interviewed Capulet? 14. Whose job did Capulet accept? 15. Who is a department manager? 16. Is there a LISP programmer who Xerox hired? 17. Whose job does Montague have? 18. How many applicants did Capulet interview? REFERENCES Barwise", |
| "authors": [ |
| { |
| "first": "Jon", |
| "middle": [], |
| "last": "", |
| "suffix": "" |
| }, |
| { |
| "first": "John", |
| "middle": [], |
| "last": "Perry", |
| "suffix": "" |
| } |
| ], |
| "year": null, |
| "venue": "", |
| "volume": "", |
| "issue": "", |
| "pages": "", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "How many applicants for the position are there? 13. Which manager interviewed Capulet? 14. Whose job did Capulet accept? 15. Who is a department manager? 16. Is there a LISP programmer who Xerox hired? 17. Whose job does Montague have? 18. How many applicants did Capulet interview? REFERENCES Barwise, Jon, and John Perry.", |
| "links": null |
| }, |
| "BIBREF10": { |
| "ref_id": "b10", |
| "title": "Situations and attitudes", |
| "authors": [], |
| "year": null, |
| "venue": "Journal of Philosophy", |
| "volume": "78", |
| "issue": "", |
| "pages": "668--692", |
| "other_ids": {}, |
| "num": null, |
| "urls": [], |
| "raw_text": "\"Situations and attitudes.\" Journal of Philosophy 78, 668-692.", |
| "links": null |
| } |
| }, |
| "ref_entries": { |
| "FIGREF0": { |
| "num": null, |
| "uris": null, |
| "text": "proposes a new set of syntactic categories of the form a/B, where ~ and 15 are categories from the basic nonterminal vocabulary of the grammar. These are called slash categories.A slash category e/B may be thought of as representing a constituent of category = with a missing internal occurrence of !5. We employ a method of introducing slash categories that was suggested by Sag (1982): a metarule stating that for every rule introducing some B under = there is a parallel rule introducing 15/~ under =/~.In other words, any constituent can have a gap of type ~\" if one of its daughter constituents does too. Wherever this would lead to a daughter constituent with the label [/~' in some 3. ~ regard was given a job not as a passive verb phrase itself but as a verb phrase containing the verb be plus a passive verb phrase containing given and a job.", |
| "type_str": "figure" |
| }, |
| "FIGREF1": { |
| "num": null, |
| "uris": null, |
| "text": "See Pullum and Gazdar (1982) for references. rule, another metarule allows a parallel rule without the ~'/;r,", |
| "type_str": "figure" |
| }, |
| "FIGREF2": { |
| "num": null, |
| "uris": null, |
| "text": "relation it did in the example above; and POS 'possession' is the same relation as that associated with have. Here the situation-type is supplied by the translation of the noun job.It is important to realize that this representation is derived without giving the noun phrase a job any special treatment. The lexical entry for give contains the information that the subject is the source of the direct object, and the direct object the possession of the indirect object. If there were lamps in our knowledge base, the derived representation of Egon gave Montague a lamp would simply be the above formula with the predicate lamp replacing employment. The possession relation would hold between Montague and some 5. Our work in this domain has been influenced by the recent papers of Barwise and Perry on \"situation semantics\"; see e.c. Barwise and Perry (1982)). base relation kept track of such matters. Two active research goals of the current project are to give all lexical entries domain independent", |
| "type_str": "figure" |
| }, |
| "FIGREF3": { |
| "num": null, |
| "uris": null, |
| "text": "S -> NP VP: (NP Vp)>\" <NPI: NP -> DET N: (DET N)> <VPI: VP -> V NP: iV NP)> <VP2: VP -> V A: A> Suppose that the lexicon associated with the above rules is: <every:DET: (LAMBDA P (LAMBDA Q (FORALL X ((P X) IMPLIES (Q X)))))> <applicant: N: APPLICANT> <interviewed: V[(RULE VP1)]: INTERVIEW> <Bill: NP: (LAMBDA P (P BILL))> <is: V[(RULE MP2)]: (BE)> <competent: A: (LAMBDA Y (EXPERT.LEVEL HIGH Y))>", |
| "type_str": "figure" |
| }, |
| "FIGREF4": { |
| "num": null, |
| "uris": null, |
| "text": "A typical parse tree S <((LAMBDA P (P BILL))(INTERVIEW X1)), <(LAMBDA P (FORALL X ((APPLICANT X) IMPLIES (P X)))) >> NP ((LAMBDA P (P BILL)))", |
| "type_str": "figure" |
| }, |
| "FIGREF5": { |
| "num": null, |
| "uris": null, |
| "text": "", |
| "type_str": "figure" |
| }, |
| "TABREF2": { |
| "type_str": "table", |
| "content": "<table><tr><td colspan=\"7\">is a set. HIRE relations are declared as properties</td></tr><tr><td colspan=\"7\">of entities within particular sorts.</td><td>For example,</td></tr><tr><td colspan=\"7\">there is an employment sort, consisting of various</td></tr><tr><td colspan=\"2\">particular</td><td/><td colspan=\"3\">employment</td><td>events,</td><td>and</td><td>an</td></tr><tr><td colspan=\"5\">employment.employee</td><td colspan=\"2\">relation</td><td>as</td><td>well</td><td>as</td></tr><tr><td colspan=\"7\">employment .organization and employment.manager</td></tr><tr><td colspan=\"2\">relations.</td><td/><td>More</td><td colspan=\"3\">conventional</td><td>relations,</td><td>like</td></tr><tr><td colspan=\"7\">employee.manager are defined as joins of the basic</td></tr><tr><td colspan=\"7\">event relations. This allows the semantics to make</td></tr><tr><td colspan=\"7\">some fairly obvious connections between verbs and</td></tr><tr><td colspan=\"7\">events (between, say, the verb work and events</td></tr><tr><td>of</td><td colspan=\"3\">employment),</td><td colspan=\"2\">and</td><td>to</td><td>represent</td><td>different</td></tr><tr><td colspan=\"7\">relations between a verb and its arguments as</td></tr><tr><td colspan=\"7\">different first-order relations between an event</td></tr><tr><td>and</td><td>its</td><td/><td colspan=\"2\">participants.</td><td/><td>Although</td><td>the</td><td>lexical</td></tr><tr><td colspan=\"2\">treatment</td><td/><td colspan=\"2\">sketched</td><td colspan=\"2\">here</td><td>is</td><td>clearly</td><td>domain</td></tr><tr><td colspan=\"3\">dependent</td><td>(the</td><td colspan=\"2\">English</td><td>verb</td><td>work</td><td>doesn't</td></tr><tr><td colspan=\"7\">necessarily involve employment events),</td><td>it was</td></tr><tr><td colspan=\"7\">chosen primarily to simplify the ontology of a first</td></tr><tr><td colspan=\"4\">implementation.</td><td colspan=\"3\">As an alternative, one might</td></tr><tr><td colspan=\"7\">consider associating work with events of a sort</td></tr><tr><td colspan=\"7\">labor, one of whose subsorts was an employment</td></tr><tr><td colspan=\"2\">event,</td><td colspan=\"2\">defining</td><td colspan=\"3\">employments</td><td>as those</td><td>labors</td></tr><tr><td colspan=\"7\">associated with an organization.</td></tr><tr><td/><td colspan=\"6\">Whichever choice one makes about the basic</td></tr><tr><td colspan=\"7\">event-types of verbs, the mapping from verbs to</td></tr><tr><td colspan=\"7\">HIRE relations cannot be direct.</td><td>Consider a</td></tr><tr><td colspan=\"7\">sentence like Anne work5 for Egon.</td><td>The HIRE</td></tr><tr><td colspan=\"4\">representation</td><td/><td colspan=\"2\">will</td><td>predicate</td><td>the</td></tr><tr><td colspan=\"5\">employment.manager</td><td colspan=\"2\">relation</td><td>of</td><td>a</td><td>particular</td></tr><tr><td colspan=\"7\">employment event and a particular manager, and</td></tr><tr><td colspan=\"7\">the employment.employee relation of that same</td></tr><tr><td colspan=\"7\">event and ,~knl,~. Yet where Egon in this example</td></tr><tr><td>is</td><td colspan=\"2\">picked</td><td>out</td><td>with</td><td/><td>the</td><td>employment .manager</td></tr><tr><td colspan=\"5\">relation, the sentence</td><td/></tr></table>", |
| "num": null, |
| "text": "All objects in the knowledge base, including events, belong to various sorts. For our purposes, a sort Anne worl<s for HP will need to pick out HP with the employment.organization", |
| "html": null |
| } |
| } |
| } |
| } |
