<?xml version="1.0"?><!DOCTYPE article SYSTEM "/project/take/software/searchbench_offline_processing/paperxml_generator/aclextractor/src/python/../resource/dtd/paperxml.dtd"><article><header><firstpageheader><page local="1" global="1"/><title>RESOLVING LEXICAL AMBIGUITY IN A DETERMINISTIC PARSER</title><pubinfo>Copyright1986 by the Association for Computational Linguistics. Permission to copy without fee all or part of this material is granted provided that the copies are not made for direct commercial advantage and theCLreference and this copyright notice are included on the first page. To copy otherwise, or to republish, requires a fee and/or specific permission. 0362-613X/86/010001-12$03.00 Computational Linguistics, Volume 12, Number 1, January-March 1986</pubinfo><author surname="Milne" givenname="Robert"><org  name="Intelligent Applications"/></author></firstpageheader><frontmatter><p><b>Resolving Lexical Ambiguity in a Deterministic Parser</b></p><p><b>Robert Milne</b></p><p><b>Intelligent Applications </b><b>10 </b><b>Charlotte Square Edinburgh </b><b>eh2 4dr </b><b>Scotland</b></p></frontmatter><abstract><b>Lexical ambiguity and especially part-of-speech ambiguity is the source of much non-determinism in parsing. As a result, the resolution of lexical ambiguity presents deterministic parsing with a major test. If deterministic parsing is to be viable, it must be shown that lexical ambiguity can be resolved easily deterministically. In this paper, it is shown that Marcus's "diagnostics" can be handled without any mechanisms beyond what is required to parse grammatical sentences and reject ungrammatical sentences. It is also shown that many other classes of ambiguity can be easily resolved as well.</b> </abstract></header><body><section number="1" title="Introduction"><p>Lexical ambiguity, and especially part-of-speech ambigu­ity, is the source of much non-determinism in parsing. As a result, the resolution of lexical ambiguity presents deterministic parsing (Marcus 1980) with a major test. If deterministic parsing is to be viable, it should be shown that lexical ambiguity can be resolved deterministically for many situations in which people do not have trouble. In this paper, it is shown that Marcus's "diagnostics" can be handled without any mechanisms beyond what is required to parse grammatical sentences and reject ungrammatical sentences and that many other classes of ambiguity can be easily resolved as well. This result is possible because of the constraints on English from word order and number agreement.</p><p>Although many high-level constituents can be "moved" in English, the lower-level structure of some constituents is relatively fixed. For example, after a determiner, one expects a noun rather than a verb. In this paper we also wish to ask, "How might this low-level fixed order assist in the resolution of ambiguity?" We will not give a definite answer to this question, but will see that it is extremely useful in the resolution of ambigu­ity.</p><p>The examples of ambiguity shown in this paper seem to cause no apparent problems to a person reading them. That is, all of these examples read easily and certainly do not exhibit the garden path effect, except, of course, the examples that are intended to be difficult. If a parser is to be psychologically plausible, then it is desirable that it handle these examples in such a way as to explain why people have no apparent difficulty with most sentences, despite the inherent ambiguity in them.</p><p>In parsing English, one of the major causes of non-determinism is part-of-speech ambiguity. If a word can be two parts of speech, then a non-deterministic parser may have to explore both possibilities. If one claims to be able to parse English deterministically, then the reso­lution of part-of-speech ambiguity is a very important area.</p><p>It should be noted that a non-deterministic parser does not need to tackle the problem of local part-of-speech ambiguity. If it should make an error, then it can back­track and correct it. Alternatively, it could maintain all possible parses at once and throw some of them away. In deterministic parsing we are not allowed to use either backtracking or parallelism. Although this problem has been investigated for many non-deterministic parsers, it has not been the critical problem that it is for determinis­tic parsing. To handle ambiguity deterministically, we must never make an error. As a result, our methods of disambiguation must be reliable. We will see that many cases of ambiguity can be resolved using standard tech­niques that have been applied to non-deterministic parsers.</p><p>If it is possible to handle all the examples of local ambiguity presented here, with no additional mechanism, device or feature than is needed for ordinary sentence parsing, then our goal above can be considered met. One possible explanation for the fact that people do not notice local ambiguities may be that there is no special mechanism needed for them, so that nothing differing from normal parsing is necessary.<page local="2" global="2"/></p><p>Conversely, if it is necessary to add special mech­anisms and routines to the parser just to handle these examples of ambiguity, then this will not explain how people can understand these examples so well and it can be considered a weakness in the model.</p><p>To say part-of-speech ambiguity can be handled deterministically but with the use of special mechanisms would be no surprise and not very important. To say one can handle part-of-speech ambiguity deterministically with no special mechanisms is a more significant claim. In this paper it is indeed suggested that many cases of part-of-speech ambiguity can be handled by the parser with no special mechanisms.</p><p>This paper is a summary of a section of the author's Ph.D. thesis (Milne 1983) with the same title and describes work done at the University of Edinburgh. That thesis presents ROB1E, a deterministic parser that is able to resolve lexical ambiguities and that is fully imple­mented in <b>PROLOG. ROBIE </b>has two lookahead buffers and does not use Marcus's Attention Shift mechanism. This means that <b>ROBIE </b>scans the current token and one more of lookahead. <b>PARSIFAL </b>scanned the current token and two lookahead cells. In this paper, only local ambiguities are addressed, that is, ambiguities that can be resolved within the sentence. Global ambiguities, which require context to resolve, are not discussed. For this paper, it is assumed that the reader is familiar with deter­ministic parsing and no other understanding of specific parsing mechanisms is assumed.</p><p>In the rest of this paper, we look at lexical ambiguity from simple examples to more complex ones. We start with how words are defined within the parser to be ambiguous and how the morphology can be used to resolve ambiguities. Next we look at how word order and finally various types of agreement can be used to resolve most remaining ambiguities.</p></section><section number="2" title="Syntactic Context 2 .1 word data structures"><p>As a first approach to handling ambiguity, it was asked, "If we construct a compound lexical entry for each word composed of the features of each part of speech the word can have and make no alterations to the grammar, how wide a coverage of examples will we get?"</p><p>This approach was used by Winograd (1972) and was found to be very effective for the following reason. Each word has all the possible relevant features for it. There­fore, the test will succeed for each possible part of speech with which a word can be used. In this way, all applica­ble rules will match. It may be that often only one rule will match, or that the first rule tried is the correct rule. The question is, how often will the rule that matches be the correct rule?</p><p>All words in ROBIE are defined in the syntactic dictionaries. Each word has a compound lexical entry incorporating all the features for all the possible parts of speech the word could have. This is exactly as was done by Winograd (1972). For example, <i>block </i>is defined as a noun and a verb, <i>can </i>is defined as a noun, auxiliary verb, and verb, and <i>hit </i>is defined as a noun and a verb. The features for each of these parts of speech are kept in the dictionary and, when the word is looked up, they are returned as a single ordered list of features. These features are sub-grouped according to the part of speech they are associated with. Hence, when the word <i>block </i>is looked up, the result returned is both the noun and the verb definition. In this way, all possibilities are returned.</p><p>In the English language, most words can have several parts of speech. This fact must be reflected in a parser of English and we do this with the multiple meanings above. When the parser has enough information to decide which is the correct part of speech, it ignores (removes) the other possibilities. In this way, we have not built struc­ture that is later thrown away. Although some may argue that this is a form of parallelism, it seems necessary since it reflects the inherent parallelism of language.</p><subsection number="2.2" title="morphology"><p>The first part of the disambiguation process takes place in the morphology. When ROBIE identifies a word that has a morphological ending, the morphology must adjust the features of the word. For example, when <i>blocked </i>is identified, the feature "ed" must be added to the list of features for <i>block. </i>At the same time, a portion of the disambiguation takes place. If <i>block </i>is defined as both a noun and a verb, then <i>blocked </i>is not a noun. The morphology causes some features to be added, such as "ed, past" and some features to be removed such as "tenseless." As features that are no longer applicable are removed, so also are parts of speech and their associated features that are no longer applicable. For <i>blocked, </i>the features "noun, ns, n3p" will be removed and the features "adjective, ed, past" will be added.</p><p>The morphology will identify words such as adverbs, adjectives, and verbs in a similar way. The morphology used is very similar to that of Winograd (1972) and of Dewar, Bratley, and Thorne (1969); the part-of-speech additions and deletions are taken from Marcus (1980). Although this technique may seem obvious, it is included to point out that a majority of the occurrences of part-of-speech ambiguity can be resolved or reduced on the basis of the morphology alone.</p></subsection><subsection number="2.3" title="disambiguation"><p>Now that we have allowed words to have multiple parts of speech and the morphology can be used to trim some of the ambiguity, we need a simple technique for disam­biguating words to a single part of speech. Again, refer­ring to Occam's Razor, what is preferable is a simple and general technique for all types of disambiguation.</p><page local="3" global="3"/><p><b>Robert M Une</b></p><p>In <b>ROBIE </b>each rule matches the features of one or two buffer cells. (The word buffer will be used interchangea­bly with cell. That is, <b>buffer </b>and <b>cell </b>are the same concept.) If the word <i>block </i>is in the first buffer cell, then a pattern [noun] or a pattern [verb] will match. These patterns do not relate to the other possible definitions of a word. If a rule pattern has matched on the feature "noun" in the first buffer cell, then <b>ROBIE </b>assumes that this word is a noun. It would then be appropriate to disambiguate the word as a noun. This is exactly as in Winograd (1972).</p><p>In a non-deterministic parser, it is not essential to find the correct rule first. If the parser runs an incorrect rule, the parser may backtrack and change the category assignment. But in a deterministic parser, there will never be any backtracking, and this solution cannot be used.</p><p>Since <b>ROBIE </b>does not backtrack, disambiguating the word when the pattern matches will always result in the same disambiguation as if the word were disambiguated in the grammar rule. Once a rule runs assuming a buffer contains a certain part of speech, it must be used as such in the parser. The general disambiguation scheme is: if a full pattern matches a word as a certain part of speech, then it is disambiguated as that part of speech.</p><p>The compound lexical entries and pattern-matching disambiguation alone will handle many examples of ambiguity. In the rest of this paper we see just what this can do for us.</p></subsection><subsection number="2.4" title="AN EXAMPLE"><p>Given the above mechanisms - multiple definition and disambiguation by the pattern matching, let us see how a few simple examples are handled. Consider:</p><p>(1) The falling block needs painting.</p><p>We will look only at the words <i>falling </i>and <i>block </i>in this example. The word <i>falling </i>is defined as a verb and an adjective in the dictionary and <i>block </i>is defined as a noun and a verb.</p><p>While parsing this example, after the word <i>the </i>has initiated an <b>NP </b>and been attached to it as a determiner, the rules to parse adjectives are activated. The rule <b>ADJECTIVE </b>has the pattern [adj], and matches the word <i>falling. Falling </i>is then attached and disambiguated as an adjective. Recognition of <i>falling </i>as a verb does not occur. As there are no more adjectives, <b>ROBIE </b>will acti­vate the rules to parse the headnoun. <b>(ROBIE</b>'s grammar assumes that all words between the first noun and the head noun of an <b>NP </b>are nouns; see section 2.6.) The rule <b>NOUN </b>with the pattern [noun] will match on the word <i>block, </i>and it will be attached as a noun. Hence <i>block </i>will also be disambiguated without the verb use being consid­ered by <b>ROBIE.</b></p><p>Other ambiguities inside the noun phrase will be handled in a similar way. This approach will usually cover    the    situation    of    singular    head nouns, verb/adjective ambiguity and many other pre-nominal ambiguities. This works because the noun phrase has a very strict word order. When an ambiguous word is found, only one of its meanings will be appropriate to the word order of the noun phrase at that point. This approach can be thought of as an extension of the basic approach of the Harvard Predictive Analyzer (Kuno 1965).</p><p>This strategy will also often disambiguate main verbs. For example, consider the following sentences:</p><p>(2) Tom hit Mary.</p><p>(3) Tom will hit Mary.</p><p>(4) The will gave the money to Mary.</p><p>In (2), <i>hit </i>is the main verb. In the dictionary, <i>hit </i>is also defined as a noun, (as in card playing). The parser will attach <i>Tom </i>as the subject of the sentence and then activate the rules for the main verb. Since <i>hit </i>has the feature "verb", it will match that rule and be attached and disambiguated as a verb. Again, other possible parts of speech are not considered.</p><p>The word <i>will </i>could be a noun or a modal as sentences (3) and (4) demonstrate. In (3), <i>will </i>cannot be part of the headnoun with <i>Tom, </i>so the <b>NP </b>will be finished as above. The rules for the auxiliary will then be activated and the word <i>will </i>then matches the pattern [modal] and is attached to the <b>AUX.</b></p><p>In (4), the word <i>will </i>is used as a noun. Since it follows the determiner, the rules for nouns will be acti­vated. The word <i>will </i>then matches the pattern [noun] and attaches to the <b>NP </b>as a noun.</p><p>The same approach will also disambiguate <i>stop </i>and <i>run </i>in the following sentence. Since <i>stop </i>is sentence initial and can be a tenseless verb, the rule <b>IMPERATIVE </b>will match, and it will be disambiguated as a verb. The word <i>run, </i>which can be a noun or a verb, will be handled as <i>will </i>in (4).</p><p>(5) Stop the run.</p></subsection><subsection number="2.5" title="THE WORD TO"><p>Now let us consider a more difficult example, the word <i>to. To </i>is defined as an auxiliary verb and a preposition in <b>ROBIE, </b>as illustrated by these sentences:</p><p>(6) I want to kiss you.</p><p>(7) I will go to the show with you.</p><p>In (6), <i>to </i>is the infinitive auxiliary, while in (7) <i>to </i>is a preposition. This analysis is based on that of Marcus (1980:118). Our two buffer cell lookahead is sufficient to disambiguate these examples.</p><p>The buffer patterns for the above sentences are:</p><doubt alpha="64.0" length="50" tooSmall="False" monospace="0.0">[to&amp;tenseless]-*■embedded VP [to&amp;ngstart]    -» PP</doubt><p>By looking at the following word, <i>to </i>can be disambigu­ated. In (7), the word <i>the </i>cannot be a tenseless verb, so the first pattern does not match. In (6), the second buffer does not have the feature "ngstart", so the rule doesn't match.<page local="4" global="4"/></p><p>However, the above patterns will accept ungrammat­ical sentences. To reject ungrammatical sentences, we can use verb subcategorisation as a supplement to the above rules. One cannot say:</p><p>(8) *I want to the school with you.</p><p>(9) *I will hit to wash you.</p><p>In English, only certain verbs can take infinitive complements. <i>To </i>can only be used as an auxiliary verb starting a VP when the verb can take an infinitive complement. Hence, by activating the rules to handle the VP usage only when the infinitive is allowed, the problem is partly reduced. Also by classifying the verb for PPs with the preposition <i>to, </i>the problem is simplified. This is merely taking advantage of subcategorisation in verb phrases. Taking advantage of this subcategorisation greatly reduces, but does not eliminate, the possible conflict.</p><p>We have seen what to do if the verb will only accept a toPP or a VP. The final difficult situation arises whenev­er the following three conditions are true:</p><p>• the verb will accept a toPP and a to VP,</p><p>• the item in the second buffer has the features "tenseless" and "ngstart" and,</p><p>• the toPP is a required modifier of the verb. Although this situation rarely arises, the above rule will make the wrong decision if the ambiguous word is being used as a noun. In this situation, ROBIE will make the wrong decision, and has no capability to better decide. By default, the principles of Right Association and Mini­mal Attachment apply as discussed in Frazier and Fodor (1978).</p><p>A free text analysis done on a cover story in TIME magazine (1978) resulted in 55 occurrences of the word <i>to. </i>The two rules mentioned above in conjunction with verb subcategorisation gave the correct interpretation of all of these. These rules were also checked on the MECHO corpus (Milne 1983) and the ASHOK corpus (Martin, Church, and Patil 1981). There were no violations of these rules in either of these.</p></subsection><subsection number="2.6" title="adjective/noun and noun/noun ambiguity"><p>Adjective/noun ambiguity is beyond the present scope of this research and is handled in a simple-minded way. If the word following the ambiguous adjective/noun word can be a noun, then the ambiguous word is used as an adjective. In other words, all conflicts are resolved in favour of the adjective usage. This problem arises in these examples:</p><p>(10) The plane is inclined at an angle of 30 degrees above the <i>horizontal.</i></p><p>(11) A block rests on a smooth <i>horizontal </i>table.</p><p>In (10), <i>horizontal </i>is a noun, while in (11), it is an adjective. The above algorithm handles these cases.</p><p>This approach takes advantage of the lookahead of the deterministic parser. A word should be used as an adjec­tive if the following word can be an adjective or a noun. However, this approach would fail on examples such as:</p><p>(12) The old can get in for half price.</p><p>(13) The large student residence blocks my view.</p></subsection><subsection number="2.7" title="why do these techniques work?"><p>In this section we have seen many examples of the reso­lution of ambiguity. To handle these examples, we mere­ly constructed a compound lexical entry for each word, composed of the features of each part of speech the word could be and allowed the pattern matching to perform the disambiguation. This technique has been used by Winograd (1972). Why does this work so well?</p><p>English has a fairly strict structural order for all the examples presented here. Because of this, in each exam­ple we have seen, the use of the word as a different part of speech would be ungrammatical. Although these tech­niques have been used for non-deterministic parsers, their effectiveness has not been investigated for a deter­ministic parser.</p><p>Most ambiguities are not recognised by people because only one of the alternatives is grammatical. In many situations, when fixed constituent structure is taken into account, other uses of an ambiguous word are not possible and probably not even recognised. Since fixed constituent structure rules out most alternatives, we have been able to handle the examples in this paper without any special mechanisms. In the introduction to this paper, it was stated that a clean and simple method of handling ambiguity was desired. I feel that this goal has been met for these examples.</p></subsection></section><section number="3" title="The Role of Agreement in Handling Ambiguity"><p>Using the simple techniques presented in the last sections, we can handle many cases of part-of-speech ambiguity, but there are many examples we cannot resolve. For example, the second of each pair of sentences below would be disambiguated incorrectly.</p><p>(14) I know that boy is bad.</p><p>(15) I know that boys are bad.</p><doubt alpha="57.1" length="21" tooSmall="False" monospace="0.0">(16) What boy did it?</doubt><p>(17) What boys do is not my business.</p><p>(18) The trash can be smelly.</p><p>(19) The trash can was smelly.</p><p>Many people wonder what role person/number codes and the relatively rigid constituent structure in the verb group play in English. In this section, we will explore their role by attempting to answer the question, "What use is the fixed structure of the verb group and person/number codes?"<page local="5" global="5"/></p><subsection number="3.1" title="UNGRAMMATICAL SENTENCES"><p>Before we proceed, let us look at an assumption Marcus made in his parser, that it would be given only grammat­ical sentences. This assumption makes life easy for someone writing a grammar, since there is no need to worry about grammatical checking. Hence no provision was made for ungrammatical sentences and the original parser accepted such examples as:</p><p>(20) *A blocks are red.</p><p>(21) *The boy hit the girl the boy the girl.</p><doubt alpha="54.5" length="22" tooSmall="False" monospace="0.0">(22) *Are the boy run?</doubt><p>This simplification causes no problems in most sentences, but can lead to trouble in more difficult exam­ples. If the parser's grammar is loosely formulated because it assumes it will be given grammatical examples only, then ungrammatical sentences may be accepted. If the syntactic analysis accepts ungrammatical sentences as grammatical, then it is making an error. Using grammat­ical constraints actually helps parsing efficiency and disambiguation. In the next sections we look at the consequences of this assumption as well as those of rejecting ungrammatical sentences.</p></subsection><subsection number="3.2" title="SUBJECT/VERB AGREEMENT"><p>We know that the verb group has a complicated but rela­tively fixed constituent structure. Although verbals have many forms, they must be mixed in a certain rigid order. We also know that the first finite verbal element must agree with the subject in person and number. That is, one cannot say:</p><p>(23) The boy are run.</p><p>(24) The boy will had been run.</p><p>(25) The boys had are red. etc.</p><p>While Marcus's parser enforced these observations to some extent, he did not follow them throughout his parser. We want to enforce this agreement throughout ROBIE. Checking the finite or main verb, to be sure that it agrees in number with the subject, will lead to the rejection of the above examples. This was done by adding the agreement requirement into the pattern for each relevant rule as will be explained later.</p><p>Buffers 1 and 2 must agree before a rule relating the subject and verb can match. This check looks at the number code of the NP and the person/number code of the verb and checks whether they agree. The routine for subject/verb agreement is very general and is used by all the subject/verb rules. The routine can only check the grammatical features of the buffers.</p></subsection><subsection number="3.3" title="MARCUS'S DIAGNOSTICS"><p>Marcus (1980) did handle some part-of-speech ambigui­ties. The words <i>to, what, which, that, </i>and <i>have </i>could all be used as several parts of speech.  For each of these words he also used a <b>Diagnostic </b>rule. These Diagnostic rules matched when the word they were to diagnose arrived in the first buffer position and the appropriate packets were active. Each diagnostic would examine the features of the three buffers cells and the contents of the Active Node Stack. Once the diagnostic decided which part of speech the word was being used as, it either added the appropriate features, or explicitly ran a gram­mar rule. Marcus did not give each word a compound lexical entry as we have done here.</p><p>Most of the grammar rules in his parser were simple and elegant, but the diagnostics tended to be very complex and contained many conditionals. In some cases they also seemed rather ad hoc and did not meet the goal of a simple, elegant method of handling ambiguity.</p><p>For example, consider the THAT-DIAGNOSTIC:</p><p>[that][np] - in the Packet CPOOL (Clause pool of rules) "If   there is no determiner of second and there is not a qp of second and the nbar of 2nd is none of massn.npl</p><p>and 2nd is not-modifiable then attach as det else if c is nbar then label 1st pronoun, relative pronoun else label 1st complementiser."</p><doubt alpha="35.3" length="17" tooSmall="False" monospace="0.0">(Marcus 1980:291)</doubt><p>Notice that if the word <i>that </i>were to be used as a deter­miner, then it would be attached after the NP was built! This is his primary rule for disambiguating the word <i>that. </i>Marcus's parser also had three other rules to handle different cases.</p><p>It seems that these rules did not "elegantly capture generalisations" as did the rest of his parser. I consider these rules undesirable and feel that they should be corrected to comply with my criteria for simple and elegant techniques in resolving ambiguity. I wanted a method that used no special mechanism, or routine, other than that needed to parse grammatical sentences. These diagnostics are certainly special mechanisms and do not meet this goal. Can we cover the same examples in a more simple and principled way?</p><p>In this section, we look at each of these diagnostics in turn and show how they have been replaced in the newer model. We also look at a few other examples of ambigui­ty which Marcus did not handle, but are related to our discussion here.</p></subsection><subsection number="3.4" title="HANDLING THE WORD TO"><p>The handling of <i>to </i>by Marcus's diagnostic can be replaced by the method outlined in Section 2.5. This method was motivated to handle grammatical sentences and meets our criterion for a simple approach.</p></subsection><subsection number="3.5" title="HANDLING WHAT AND WHICH"><p>For both <i>what </i>and <i>which, </i>the ambiguity lies between a relative pronoun and a determiner. The following exam­ples show various uses of both words:</p><page local="6" global="6"/><p>then label 1st pronoun, relative pronoun (26) Which boy wants a fish? <b>det</b> (27) Which boys want fish? <b>det</b> (28) The river which I saw has many fish. <b>rel. pron.</b></p><doubt alpha="66.7" length="30" tooSmall="False" monospace="0.0">(29) What boy wants a fish?det</doubt><p>(30) What boys want is fish. <b>rel. pron.</b></p><p>There is some debate about the part of speech to be assigned the word <i>which. </i>Some linguists consider it to be a quantifier (Chomsky 1965), while others consider it to be a determiner (Akmajian and Heny 1975, Chapter 8). We shall adopt the determiner analysis, making the prob­lems for <i>what </i>and <i>which </i>similar.</p><p>To determine the correct part of speech for these two words, Marcus (1980:286) used the following diagnos­tics:</p><p>[which] — in the packet CPOOL "If   the NP above Current Node is not modified else label 1st quant,ngstart,ns,wh,npl." [what][t] ■* in the packet NPOOL "If   2nd is ngstart and 2nd is not det</p><p>then label 1st det,ns,npl,n3p,wh; activate parse_det else label 1st pronoun,relpron,wh."</p><p>These diagnostics would make the word in question a relative pronoun if it occurred after a headnoun, or a determiner if the word occurred at the start of a possible noun phrase.</p><p>If we follow the approach in the last section, and give each word a compound lexical entry composed of the determiner and relative pronoun features, we find that these words are always made determiners unless they occur immediately after a headnoun. In other words, the <i>which </i>examples are all parsed correctly, but (30) is parsed incorrectly. This happens because the determiner rule will always try to match before the rule for WH ques­tions can take effect. This simple step gives the correct analysis if the ambiguous word is to be a determiner, but will still err on (30).</p><p>The rule to parse a relative pronoun and start a rela­tive clause is active only after the headnoun has been found. At this time, the rule for determiners is not active. Therefore, if the word <i>what </i>or <i>which </i>is present after a headnoun, the only rule that can match is the rule to use it as a relative pronoun, and it will be used as a relative pronoun. We have resolved the simple case of <i>what </i>as a relative pronoun using only the simple tech­niques of the last section. For these sentences</p><doubt alpha="60.9" length="23" tooSmall="False" monospace="0.0">(31) What block is red?</doubt><doubt alpha="60.9" length="23" tooSmall="False" monospace="0.0">(32) Which boy hit her?</doubt><doubt alpha="64.3" length="28" tooSmall="False" monospace="0.0">(33) Which is the right one?</doubt><p>ROBIE produces the correct analysis, but still errs on (30). This error is because <i>what </i>is being used as a rela­tive pronoun but does not follow a headnoun. Without any additional changes to the parser, we get two things. Firstly, if the word occurs after the headnoun, then the</p><p>NP-COMPLETE packet rules are active, and it will be a relative pronoun. In fact, since relative clauses can occur only after the end of an NP, this correctly resolves the relative pronoun uses. If the word occurs at the start of an NP, then it will be made a determiner.</p><p>This approach has exactly the same effect and cover­age as did Marcus's diagnostics, but we have not needed any special rules to implement it. It will now provide the correct interpretation for <i>which, </i>but will make some errors for the word <i>what. </i>Marcus's <b>what-diagnostic </b>will treat <i>what </i>as a determiner whenever the item in the second buffer could start a NP. This is usually correct, but <i>what </i>will be treated as a determiner in all of the following:</p><p>(34) What boys want is fish.</p><doubt alpha="65.4" length="26" tooSmall="False" monospace="0.0">(35) What blocks the road?</doubt><doubt alpha="65.2" length="23" tooSmall="False" monospace="0.0">(36) What climbs trees?</doubt><doubt alpha="63.0" length="27" tooSmall="False" monospace="0.0">(37) What boys did you see?</doubt><doubt alpha="66.7" length="33" tooSmall="False" monospace="0.0">(38) What blocks are in the road?</doubt><doubt alpha="64.3" length="28" tooSmall="False" monospace="0.0">(39) What climbs did you do?</doubt><p>In this paper, we are adopting the following analysis for WH clefts such as (34). The initial WH word, <i>what </i>is a relative pronoun and attached as the WH-COMP of the subject S node. The subject is the phrase <i>What boys want. </i>The main verb of the sentence is <i>is </i>and the complement <i>fish. </i>The exact details are not important, only that the word <i>what </i>or <i>which </i>is a not determiner at the start of a WH cleft.</p><p>In sentences (34-36), the word <i>what </i>is not used as a determiner. In the analysis we are using, it is a relative pronoun and is used as the WH-COMP for the S. In sentences (37-39), the word <i>what </i>is used as a determiner. Marcus (1980:286) admits that this diagnostic produces the incorrect result in this case. His diagnostic will make <i>what </i>a determiner in all of these examples, as will my analysis.</p><p>One can also see that each of the above pairs is a pair of potential garden path sentences. For each pair, the two buffers contain the same words. Hence our two-buf­fer lookahead is not sufficient to choose the correct usage of the word <i>what. </i>Using only two or three buffers, there is no way to make <i>what </i>a relative pronoun when the headnoun is plural but a determiner when it is singular for all arbitrary sentences.</p><p>With regard to the Semantic Checking Hypothesis (Milne 1982) then, it is suggested that this decision is based on non-syntactic information. I believe that into­nation is critical in these examples. Unfortunately there is insufficient experimental evidence to determine for certain whether this is true. Finally, the problem of <i>what </i>and <i>which </i>as sentence initials, with no noun in the second buffer seems to arise very rarely. I have found no exam­ples of this problem in free text analysis.</p><p>The current parser (ROBIE) cannot obtain the extra information provided by intonation to help resolve this case. As a result it follows Marcus's diagnostic and makes <i>what </i>a determiner in each of the above cases.</p><page local="7" global="7"/><p><b>Robert MUne</b></p><p>This is because <i>what </i>is defined as a determiner that can agree with either a singular noun or a plural noun, as it was in Marcus's parser.</p></subsection><subsection number="3.6" title="HANDLING THAT"><p>In ROBIE, <i>that </i>is defined as a singular determiner, a pronoun, a relative pronoun, and a complementiser. Marcus had four diagnostics to handle the word <i>that. </i>We have seen one of these at the start of this section. In this sub-section we see how these four diagnostics can be replaced in a simple way. Let us consider how to handle the uses of <i>that </i>one at a time.</p><p>Firstly, as a determiner. The following sentences illus­trate the problem in identifying this usage.</p><p>(40) I know that boy should do it.</p><p>(41) 1 know that boys should do it.</p><p>Marcus assumed that PARSIFAL would be given only grammatical sentences to parse. If determiner/number agreement is not given to a parser, then it will, incorrect­ly, make <i>that </i>a determiner in (41), producing the wrong analysis. The way to prevent this is to enforce number agreement in the rule DETERMINER by insisting that the determiner agree with the noun in number. The deter­miner usage will be grammatical only when the headnoun has the same number. If we make this a condition for the rule to match, then <i>that </i>will not be made a determiner in (41) and ROBIE will get the correct parse.</p><p>For this case, the agreement check would make sure that one of the following patterns match:</p><doubt alpha="61.5" length="39" tooSmall="False" monospace="0.0">[det,ns] [noun,ns] [det.npl] [noun.npl]</doubt><p>The above two cases are handled properly because number agreement blocks the interpretation of the (41) as a determiner. This approach leads to the correct pref­erence, when there is an ambiguity and accounts for the difficulty in (42) versus (43):</p><p>(42) That deer ate everything in my garden surprised me.</p><p>(43) That deer ate everything in my garden last night.</p><p>The second experiment in Milne (1983), showed that (42) is a garden path sentence, while (43) is not. In both sentences, it is believed the subject uses the word <i>that </i>as a determiner. <i>Deer </i>is both singular and plural, so it fits the above rule. In (42), <i>that </i>must be used as a complem­entiser to make the sentence grammatical. The approach outlined above will use <i>that </i>as a determiner in an ambig­uous case such as this.</p><p>These two simple techniques, word order and agree­ment, are sufficient to handle all the examples we have just presented. In addition, free text analysis has shown no violations to this approach (Milne 1983). These tech­niques provide the same coverage as Marcus's diagnostic, with the added bonus that the determiner is attached before the NP is built.</p><p><i>That </i>can only be a complementiser when a <i>that S- </i>is expected. Hence the rules using <i>that </i>to start an embed­ded sentence are only activated when the verb has the feature THAT-COMP. The rules in THAT-COMP will fire when <i>that </i>is followed by something that can start an NP. This ensures that the S- will have a subject and means that <i>that </i>will be taken as a pronoun in the following sentences:</p><p>(44) I know that hit Mary.</p><p>(45) I know that will be true.</p><p>but it will be taken as a complementiser in these sentences:</p><p>(46) I know that boys are mean.</p><p>(47) I know that Tom will hit Mary.</p><p>It seems that, unless the S- has a subject, the pronoun use of <i>that </i>is preferred. Otherwise one would have a complementiser followed by a trace, rather than a unmarked complementiser, followed by a pronoun. This rule provides more complete coverage than Marcus's diagnostic since it examines the second buffer.</p><p>The rule to handle pronouns in general is of low prior­ity and will only fire after all other uses have failed to match. <i>That </i>is treated in the same way.</p><p><i>That </i>will be identified as a relative pronoun only if it occurs after a headnoun and the packet NP-COMPLETE is active. This situation will be handled in the same manner as the usual relative clause rules and will then cover:</p><p>(48) I know the boy that you saw.</p><p>(49) I know the boy that hit you.</p><p>The most difficult case for <i>that </i>is when the verb is subcategorised:</p><doubt alpha="80.0" length="5" tooSmall="False" monospace="0.0">VNPS-</doubt><p>That is, it can take an NP subject, followed by a <i>that </i>S-. For these examples, ROBIE may have to decide if the series of words following <i>that </i>is a relative clause or an embedded sentence.</p><p>In the following sentences, the lookahead would have to be more than three buffers. (Brackets indicate words in the buffers. The last word is the disambiguating word.)</p><doubt alpha="66.0" length="50" tooSmall="False" monospace="0.0">(50) I told the girl [that][the][boy] hit thestory</doubt><doubt alpha="64.0" length="50" tooSmall="False" monospace="0.0">(51) 1 told the girl [that][the][boy] will kissher</doubt><p>It can be seen that in these sentences the disambiguat­ing word is outside our three buffers. How do people handle these, and what should our parser do? In Milne (1983) it was shown that when the syntax could not resolve the ambiguity with its two-buffer lookahead, the decision of which interpretation to use might be made using non-syntactic information. It was also stated that if context can affect the interpretation of the sentence, then non-syntactic information is being used to select the<page local="8" global="8"/></p><p><b>Robert MUne</b></p><p>interpretation. The reader can experiment for himself and see that context does affect the interpretation of these sentences. Therefore it is predicted that non-syn­tactic information is being used to interpret these sentences, and that this problem should be resolved not on a semantic basis but on a non-syntactic one.</p><p>This explains why some of these examples cause diffi­culty and others do not. The psychological evidence from cases using <i>that </i>is scant, and I feel no conclusions can be reached here. My theory predicts that context will strongly affect these examples and, if they are strongly biased to the incorrect reading, a garden path should result.</p><p>One well-known example in this area is (52):</p><p>(52) I told the girl that I liked the story.</p><p>(53) I told the girl whom I liked the story.</p><p>(54) I told the girl the story that I liked.</p><p>These examples were tested in Milne (1983). The results suggested that (52) was read faster than the other two examples. Many of the subjects were questioned informally after the experiment about their interpretation of the sentence. All reported only one meaning; the S-reading. None of the subjects said that they noticed the relative clause reading, hence the result. The experiment however, was not designed formally to distinguish these.</p><p>To handle the examples we have seen in this section, Marcus had four diagnostics, one of which was very complicated. I have just shown how to handle all four cases of <i>that </i>without any special rules, merely substitut­ing enforced agreement and rejecting ungrammatical sentences.</p></subsection><subsection number="3.7" title="HANDLING THE WORD HA VE"><p>Let us now look at the elimination of Marcus's HAVE-DIAGNOSTIC in relation to the use of agreement we have been discussing in this section. The problem with <i>have </i>is illustrated by the following sentences:</p><p>(55) Have the students take the exam.</p><p>(56) Have the students taken the exam?</p><p>In these, we must decide if <i>have </i>is an auxiliary verb or a main verb and whether the sentence is a yes-no question or an imperative. The sentences have the same initial string until the final morpheme on <i>take. </i>To handle this case, Marcus (1980:211) used this rule:</p><p>"RULE HAVE-DIAG PRIORITY: 5 IN SS-START</p><doubt alpha="61.5" length="26" tooSmall="False" monospace="0.0">[have,tenseless][np][t] -»</doubt><p><b>If 2nd is ns,n3p or 3rd is tenseless</b></p><p><b>then run imperative next else If 3rd is not verb</b></p><p><b>then run yes-no-question next else if not sure, assume it's a y/n-q and run yes-no-question next"."</b></p><p>This rule seems to be necessary in order to distinguish between the question and the imperative. If one tries to ascertain exactly what occurs, the apparent complexity is revealed. Note also that Marcus's rule defaults to a yes-no question twice in this diagnostic. The following sentences illustrate the distinction this rule makes.</p><p>(57) Have the boy take the exam.</p><p>(58) Have the boy taken the exam.</p><p>(59) Have the boys take the exam.</p><p>(60) Have the boys taken the exam?</p><p>It can be seen that YES-NO QUESTION should run only when the NP following is plural and the verb has "en" (i.e., <i>taken). </i>[Only (60) has a plural noun, <i>the boys, </i>and the verb <i>taken.] </i>This can also be understood as: the sentence is an imperative if the item in the 2nd buffer is not plural and the verb is tenseless. Thus, the first three examples above are Imperatives because either the noun <i>(boy) </i>is singular (57 and 58) or the verb is tenseless (59). The second part of the rule takes care of the fact that the third buffer must contain a verb for the imperative, as this would be the main verb of the embedded sentential object.</p><p>Let us look more closely at the reason why only (60) is a question. Firstly, if the sentence is a yes-no question, then aux-inversion must occur. When this happens, <i>Have </i>will be adjacent to the verb that was in the third buffer. In order for ROBIE to continue, the verb must have an "en" ending, or <i>have </i>and the next verb will not agree in aspect. This is the basis for discrimination in the earlier examples (57-60).</p><p>Secondly, in (57) and (58), the noun phrases are singular and both sentences are imperatives. Had the sentence been a yes-no question, <i>have </i>would need to agree with the subject, which must then be plural.</p><p>Hence, in effect, Marcus's rule checks for number agreement between the subject and verb, and checks that the fixed order of the verb group is obeyed. Let us now look at other situations where this is necessary.</p><p>PARSIFAL would accept the following ungrammatical strings:</p><doubt alpha="59.3" length="27" tooSmall="False" monospace="0.0">(61) * Are the boy running?</doubt><doubt alpha="56.5" length="23" tooSmall="False" monospace="0.0">(62) *Has the boys run?</doubt><doubt alpha="61.5" length="26" tooSmall="False" monospace="0.0">(63) *Has the boy kissing?</doubt><doubt alpha="56.5" length="23" tooSmall="False" monospace="0.0">(64) *Has the boy kiss?</doubt><p>For a yes-no question, the inverted auxiliary must agree with the verb after it has been inverted. To stop these ungrammatical constructions, we must enforce verb agreement. The pattern for the rule YES-NO QUESTION should be:</p><p><b>[auxverb][np][verb], agree(auxverb,verb),agree(verb,np).</b></p><p>This constraint enforces agreement of the verb and auxiliary verb and the subject and verb. Again this check is based only on the linguistic features of the buffers.</p><p>Such a constraint effectively blocks the ungrammatical constructions. (The parser will fail if the auxiliary has been inverted, since the auxiliary will not be parsed.) Also the subject NP must agree with the auxiliary verb, so we can also add "agree(auxverb,np)" to the rule, as we did with the HAVE-DIAGNOSTIC!<page local="9" global="9"/> So, by correcting the yes-no question rule, the HAVE-DIAGNOSTIC is redundant.</p><p>In this section we have seen that Marcus's HAVE-DIAGNOSTIC can be replaced by merely exploit­ing agreement. It should be pointed out that although this approach has the same coverage as Marcus's diag­nostic, it is wrong in some cases. Milne (1983) has a full discussion.</p></subsection><subsection number="3.8" title="PLURAL HEAD NOUNS"><p>There is a class of ambiguities that can be resolved mere­ly by enforcing subject/verb agreement. In this section, we see an example from the class of words with the features noun, verb, final-s (plural). If we have two words that can be a plural noun or a singular verb, we can enumerate four cases. Let us look at these possibil­ities and see that these cases can be disambiguated by simple rules using subject/verb agreement. The follow­ing examples illustrate all the possibilities:</p><p>(65) The soup pot cover handle screw is red.</p><p>(66) The soup pot cover handles screw tightly.</p><p>(67) The soup pot cover handles screws tightly. {68} The soup pot cover handle screws tightly. {69} The soup pot cover handle screws are red.</p><p>Each of the words <i>pot, cover, handle, </i>and <i>screw </i>can be either a noun or a verb. The "end of constituent" prob­lem is to find out which word is used as the verb and which words make up the complex headnoun. The possi­ble distributions of the morpheme "s" among two words gives us four cases. We deal with each of these in turn.</p><p>Case 1: In (65) each noun is singular. For this case all ambiguous words must be nouns and part of the head­noun. Due to subject/verb agreement, a singular noun must match a 3rd person singular (v3s) verb, i.e, one without the letter "s". This case excludes that possibility since none of the words have an "s" at the end. Hence they must all be nouns.</p><p>Case 2: In (66) <i>handles </i>is a plural noun and each word before it must be a noun. When a singular noun/verb word follows <i>handles, </i>the word <i>(screw) </i>must be a verb and <i>handles </i>is the last of the headnouns. It is not possi­ble to use <i>handles </i>in this situation as a verb, and <i>screw </i>as a noun because of subject/verb agreement.</p><p>Case 3: The examples in this case have two consec­utive plural nouns as in (67), where both words have noun/verb ambiguity. (Do not confuse plural "s" with possessive "'s").</p><p>When the first plural is a noun, then the second one can be a verb only if it is part of a different constituent. Examples of this are the following. (Sentences beginning with "?" are considered grammatical but unacceptable to most readers.) (70) ?The soup pot machine handles screws easily.</p><p>(71) The soup pot machine handles screw easily.</p><p>(72) Which years do you have costs figures for?</p><p>(73) Do you have a count of the number of sales requests and the number of requests filled?</p><doubt alpha="51.7" length="58" tooSmall="False" monospace="0.0">[(72) and (73) are from Martin, Church, and Patil (1981).]</doubt><p>Because there is a non-plural headnoun followed by a plural headnoun, this case is really a subset of Case 4. In general, the problems and issues for Case 4 dominate the resolution of this ambiguity.</p><p>Case 4: Sentences (68) and (69) both have the same word initial string until after <i>screws, </i>but in (68) <i>screws </i>is a verb while in (69) <i>screws </i>is part of the headnoun. In this situation, where the final word in a series is plural, each word before it must be a noun. The word itself can be either a noun or a verb, depending on what follows. These can be recognised as a pair of potential garden path sentences, as discussed in Milne (1982). Therefore, this is the case to which the Semantic Checking Hypoth­esis applies and the predictions of Milne (1982) apply.</p><p>In that paper, the idea of <b>potential garden path sentences </b>is presented. These are sentences that may or may not lead to a garden path. Each garden path sentence has a partner, which is similar but not a garden path. It is proposed that the decision as to how to resolve the ambiguity that may lead to a garden path should be made by semantics and not by syntax. This theory is called the Semantic Checking Hypothesis. For full details see Milne (1983).</p><p>In this section, we have looked at resolving a simple case of noun/verb ambiguity. In order to resolve this ambiguity, it was necessary merely to exploit agreement between the subject and verb in number and person.</p><p>Due to number and subject verb agreement, these facts have a linguistic base. They rely on the fact that a final "s" marks a plural noun but a singular verb. If the verb is v3s (verb agrees with a 3rd person, singular noun, as with the "s"), then the subject of the verb must be singular, or else the sentence is ungrammatical. This is why all the words before the v3s word must be nouns. If any of these words were used as a verb, then subject-verb agreement would be violated. This is why (67) is ungrammatical. If the verb is v-3s (agrees with any noun phrase except 3rd person, singular i.e., no "s"), then the subject cannot be singular. (65) has no plural subject and so cannot have a v-3s verb. In (66) <i>handles </i>provides a plural subject, so <i>screw, </i>which is v-3s, can agree.</p></subsection><subsection number="3.9" title="NOUN/MODAL AMBIGUITY"><p>We now consider noun/modal ambiguity as demon­strated by <i>can </i>and <i>will. </i>Both can be either a noun or a modal (i.e., <i>could, should, would, can, will, might, </i>etc.):</p><p>(74) The trash can was taken out.</p><p>(75) The trash can be taken out.</p><p>(76) The paper will was destroyed.</p><p>(77) The paper will be destroyed.</p><page local="10" global="10"/><p><b>Robert MUne</b></p><p>Each of these words is entered in the dictionary both as a noun and a modal. Due to agreement requirements, the modal/noun word can only be grammatically used as a modal if the word following it is a tenseless verb, i.e., the pattern:</p><p>[modal] [tenseless] — modal usage applies. Handling noun/modal ambiguity can be quite easy; when the noun modal word appears in the first buffer one merely has to look at the contents of the second buffer to see if it contains a tenseless verb. This can be complicated, though, if the auxiliary is inverted or the sentence is an imperative. The following examples show how this can arise:</p><p>(78) Let the paper will be read.</p><doubt alpha="65.7" length="35" tooSmall="False" monospace="0.0">(79) Will the paper can be re-used?</doubt><p>In sentence (78) the fragment <i>Let the paper </i>implies that <i>will </i>can only be used as a noun, as the sentence already has one tensed verb. In the parser, the noun/modal word is first encountered inside the NP packets and the parser must decide whether to use the word as part of the headnoun or to leave it in the buffer to be used as a modal verb. These rules do not know whether a verb has been found previously. Hence, not all information from the sentence is used. If all the infor­mation is available at the time the noun/modal ambiguity is being resolved, these sentences would be unambiguous and people would have no trouble reading them.</p><p>Subjects were asked to read the above examples in the second experiment presented in Milne (1982). The results showed convincingly that they are potential garden paths. Many naive readers had considerably more difficulty with them than with their more straight­forward counterparts. This was predicted for reasons explained below.</p><p>This result seems surprising. If the subjects used all information available at the time the noun/modal word was encountered, then they should have had no trouble with these sentences. The fact that these are garden paths indicates that the readers did not use all the infor­mation available to them. Notice also that the ambiguity can be reformulated as: "Do we have the end of a noun phrase, or a complex headnoun?"</p><p>We have already seen a case where people do not seem to use all the information available to them. In Milne (1983), several end-of-NP problems were presented that could lead to a garden path. In each of these, it was shown that the ambiguity was resolved on the basis of non-syntactic information, without regard to the following words in the sentence. In other words, we saw that the reader did not use all the information avail­able. There is one crucial difference though. In the previous cases, non-syntactic information was used because the syntactic processor with its limited lookahead was sometimes unable to choose the correct alternative.</p><p>In this case, the information necessary has already been absorbed by the parser.</p><p>This suggests that the choice of alternatives is made locally inside the NP parsing rules, without regard to information about the type of sentence being parsed. In other words, the two-buffer pattern applies regardless of the rest of the sentence. This assumes that a noun/modal word followed by a tenseless verb is being used as a modal. This is similar to Fodor, Bever, and Garrett's (1974) old canonical sentoid strategy: a bottom-up analysis that took every N-V combination as a new <i>S. </i>Let us look at why this might be true in the parser.</p><p>When the parser starts to parse a NP, it creates a new NP node and pushes it to the bottom item of the Active Node Stack. This operation makes the NP node the Current Active Node and parsing of the old Current Active Node is suspended. If the parser is parsing an S node, for example at the start of the sentence, then work on this node will be suspended until the NP node has been completed and dropped into the buffer.</p><p>In ROBIE, unlike PARSIFAL, the pattern matcher for the grammar rules is allowed only to inspect the gram­matical features of the two buffers. This means that the parser is unable to examine the contents of the Active Node Stack and, hence, the information that a tensed verb has already been found is unavailable to the NP parsing rules. This then suggests that the ambiguity will be resolved on the basis of local information only.</p><p>It should be pointed out that although ROBIE does not examine the Active Node Stack, the current packet reflects its contents. For example, if the parser is parsing the major S node, the packet <i>SS-VP </i>will be active, but if the parser is parsing an embedded S node, the packet Embedded-S will be active. This information can be considered to provide local context to the parsing rules. This is the same as in PARSIFAL.</p><p>This ambiguity is an end-of-NP problem and the choice of alternatives is made on the basis of limited and local information. This suggests that non-syntactic infor­mation may be used to resolve the ambiguity. There is one further possibility. The semantic choice mechanism is attempting to find the end of an NP. So far it has asked the question, "Can this item be part of the NP?" However, the end-of-NP problem can be reformulated as, "Is it better to use this as part of the NP, or as the start of the verb group?" It is conceivable that the end of NP mechanism uses <i>will </i>as the start of the verb group in the majority of occurrences, hence leading to the apparent modal preference in these examples:</p><p>(80) The trash can hit the wall.</p><p>(81) The paper will hit the table.</p><p>Due to lack of data, it is not clear exactly what people do in this situation and this would seem to provide an inter­esting area for further investigation.</p><page local="11" global="11"/><p><b>Robert MUne</b></p></subsection><subsection number="3.10" title="what about HER"><p>Another problem is the word <i>her, </i>which can be used as a pronoun or as a possessive pronoun. Note that we can say:</p><p>(82) Tom kissed her.</p><p>(83) Tom kissed her sister.</p><p>Clearly in (82) <i>her </i>is a pronoun and in (83) <i>her </i>is a possessive determiner. When multiple part-of-speech definitions were added to ROBIE and the simple disam­biguation method used, ROBIE always made <i>her </i>a posses­sive determiner.</p><p>This difficulty arose in Marcus's parser because the rule to start a NP was ordered before the rule to parse a pronoun. These rules were copied directly into ROBIE's grammar. Since the word <i>her </i>has both the features "ngstart" and "pronoun", it could match both rules. Unfortunately, as Marcus's rules were stated, it always matched the NP starting rule, and hence was used as a determiner by the parser. This indicates one problem that can arise in the writing of a parser grammar.</p><p>To handle possessive determiners, PARSIFAL and ROBIE have a rule with the pattern:</p><doubt alpha="66.7" length="9" tooSmall="False" monospace="0.0">[poss_np]</doubt><p>This rule will match a possessive pronoun after it has been made into an NP. It will also match any possessive NP, such as: <i>the boy's </i>or <i>the boy's mother's. </i>The rule then adds the feature "determiner" to the NP, making it eligi­ble for the NP starting rule. By degrading the possessive NPs to determiners, both parsers easily handle examples of left branching such as:</p><p>(84) The boy's mother's brother is his uncle.</p><p>Another problem arose in (82) because the possessive NP rule was not sufficiently constrained. It is possible to use <i>her </i>as a determiner only where the next word can be part of a noun phrase with that determiner. To enforce this, the second buffer is checked to be certain that its contents will take the determiner. Using this approach, <i>her </i>in (82) would not be converted to a possessive deter­miner. The rule DETERMINER can run only if the next item will "take a determiner".</p><p>This check is made by the syntactic category of the following word, rather than by a specially marked feature. This check could be done by having a list of all the possible categories as the pattern of the second buff­er. As an implementation detail, this is in the form of an agreement check, merely to simplify this rule and to show its generality.</p><p>The only remaining problem occurs when the verb can take one or more objects and the item after the word <i>her </i>can be either the second object, or an NP with <i>her </i>as a determiner. For example:</p><p>(85) I took her grapes.</p><p>(86) He saw her duck.</p><p>(87) I gave her food for the dog.</p><p>The examples presented above are all examples of global ambiguity, which is discussed in more detail in Milne (1983). In these cases the check of "Will the next word take a determiner?", may or may not lead to the wrong analysis. This problem also interacts with the top-down component of verb phrase parsing and the semantic restrictions presented by it.</p><p>The conflict between the determiner and possessive usage can be modelled as a conflict of rule priorities. If the possessive use is preferred, then this rule should match first. Conversely, if the object use is preferred, then the object rule should match first. Any error in reading these examples would be due to one rule having priority over the other, when the reverse should be the case. Finally, notice that with no help from either into­nation or context, either analysis is possible. That is, there is not enough information in the sentence to deter­mine a unique interpretation.</p><p>We have now shown how to replace all the diagnostics Marcus used. In doing this, we enforced number and verb agreement on the rules before they could run. This was motivated to reject ungrammatical items, rather than for the handling of ambiguity. While there are still a few problems due to global ambiguity, the approach reported here has the same coverage as Marcus's diagnostics, and provides a better explanation of why people have trouble on certain sentences.</p></subsection></section><section number="4" title="Possible Uses for Agreement in English"><p>In this paper, we have seen several occurrences of ambi­guity, for each of which we have found a parallel situ­ation that could lead to acceptance of ungrammatical sentences by ROBIE. We then used person/number codes or the fixed structure of the verb group to block these unacceptable readings. Most of our ambiguity problems were also handled by this method. Although this has been used before with non-deterministic parsers, it was not obvious that it would provide enough informa­tion to enable deterministic parsing.</p><p>Once person/number codes are taken into account, the number of potential ambiguous readings is dramat­ically reduced. In many cases, only one of the ambiguous possibilities was grammatical. It should be noted that there are a few difficult cases which we have not had time to describe in this paper; these are discussed in detail in Milne (1983).</p><p>Marcus had a few rules to resolve part of speech ambi­guity, but they were ad hoc. We have seen that we can replace these rules very simply by merely exploiting agreement.</p><p>In the introduction, it was stated that handling lexical ambiguity was a major test for deterministic parsing. In this paper we have seen that many cases of ambiguity can be resolved in a simple way. This is possible because of the constraints imposed by number agreement and word order.   In fact, many cases of the seemingly difficult problem of lexical ambiguity turn out to be easily resolved in a deterministic parser, since the deterministic parser uses more information to make decisions.<page local="12" global="12"/></p></section><references><p>Akmajian, A. and Heny, F.  1975 <i>An Introduction to the Principles of</i></p><p><i>Transformational Syntax. </i>MIT Press, Cambridge, Massachusetts. Chomsky, Noam   1965  <i>Aspects of the Theory of Syntax. </i>MIT Press,</p><doubt alpha="65.6" length="90" tooSmall="False" monospace="0.0">Cambridge, Massachusetts. Dewar, H.; Bratley, P.; and Thome, J.   1969   A Program for the</doubt><p>Syntactic Analysis of English Sentences.   <i>Communications of the</i> <i>ACM </i>12(8).</p><doubt alpha="65.6" length="64" tooSmall="False" monospace="0.0">Fodor, Jerry; Bever, T.; and Garrett, M.   1974The Psychology of</doubt><p><i>Language. </i>McGraw-Hill, New York, New York. Fodor, Janet and Frazier, Lynn 1978 The Sausage Machine: A New</p><p>Two-Stage Parsing Mode. <i>Cognition </i>6: 291-325.</p><p>Kuno, S. 1965 The Predictive Analyzer and a Path Elimination Tech­nique. <i>Communications of the ACM </i>8(10).</p><p>Marcus, Mitchell 1980 <i>A Theory of Syntactic Recognition for Natural Language. </i>MIT Press, Cambridge, Massachusetts.</p><p>Martin, William; Church, K; and Patil, R. 1981 Preliminary Analysis of a Breadth-First Parsing Algorithm: Theoretical and Experimental Results. MIT Al Lab. Presented at Modeling Human Parsing Strat­egies Symposium, Austin, Texas.</p><p>Milne, Robert 1982 Predicting Garden Path Sentences, <i>Cognitive Science </i>6: 349-373.</p><p>Milne, Robert 1983 Resolving Lexical Ambiguity in a Deterministic Parser. D.Phil. Dissertation, University of Edinburgh, Edinburgh, Scotland.</p><p>TIME 9 January 1978 Good Ole Burt; Cool-eyed Clint. Winograd, Terry   1972 <i>Understanding Natural Language. </i>Academic Press, New York, New York.</p></references></body></article>