File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/metho/94/p94-1003_metho.xml
Size: 30,168 bytes
Last Modified: 2025-10-06 14:13:54
<?xml version="1.0" standalone="yes"?> <Paper uid="P94-1003"> <Title>PRIORITY UNION AND GENERALIZATION IN DISCOURSE GRAMMARS</Title> <Section position="1" start_page="0" end_page="0" type="metho"> <SectionTitle> PRIORITY UNION AND GENERALIZATION IN DISCOURSE GRAMMARS </SectionTitle> <Paragraph position="0"/> </Section> <Section position="2" start_page="0" end_page="0" type="metho"> <SectionTitle> 2 Buccleuch Place </SectionTitle> <Paragraph position="0"> Edinburgh EH8 9LW, UK Internet: C. Grover(c)ed. ac. uk</Paragraph> </Section> <Section position="3" start_page="0" end_page="0" type="metho"> <SectionTitle> Abstract </SectionTitle> <Paragraph position="0"> We describe an implementation in Carpenter's typed feature formalism, ALE, of a discourse grammar of the kind proposed by Scha, Polanyi, et al. We examine their method for resolving parallelism-dependent anaphora and show that there is a coherent feature-structural rendition of this type of grammar which uses the operations of prwrity union and generalization. We describe an augmentation of the ALE system to encompass these operations and we show that an appropriate choice of definition for priority union gives the desired multiple output for examples of vP-ellipsis which exhibit a strict/sloppy ambiguity.</Paragraph> </Section> <Section position="4" start_page="0" end_page="17" type="metho"> <SectionTitle> 1 Discourse Grammar </SectionTitle> <Paragraph position="0"> Working broadly within the sign-based paradigm exemplified by HPSG (Pollard and Sag in press) we have been exploring computational issues for a discourse level grammar by using the ALE system (Carpenter 1993) to implement a discourse grammar. Our central model of a discourse grammar is the Linguistic Discourse Model (LDM) most often associated with Scha, Polanyi, and their co-workers (Polanyi and Scha 1984, Scha and Polanyi 1988, Priist 1992, and most recently in Priist, Scha and van den Berg 1994). In LDM rules are defined which are, in a broad sense, unification grammar rules and which combine discourse constituent units (DCUS). These are simple clauses whose syntax and underresolved semantics have been determined by a sentence grammar but whose fully resolved final form can only be calculated by their integration into the current discourse and its context. The rules of the discourse grammar act to establish the rhetorical relations between constituents and to perform resolution of those anaphors whose interpretation can be seen as a function of discourse coherence (as opposed to those whose interpretation relies on general knowledge).</Paragraph> <Paragraph position="1"> For illustrative purposes, we focus here on Prfist's rules for building one particular type of rhetorical relation, labelled &quot;list&quot; (Priist 1992). His central thesis is that for DCUs to be combined into a list they must exhibit a degree of syntactic-semantic parallelism and that this parallelism will strongly determine the way in which some kinds of anaphor are resolved. The clearest example of this is vP-ellipsis as in (la) but Priist also claims that the subject and object pronouns in (lb) and (lc) are parallelism-dependent anaphors when they occur in list structures and must therefore be resolved to the corresponding fully referential subject/object in the first member of the list.</Paragraph> <Paragraph position="2"> (1) a. Hannah likes beetles. So does Thomas.</Paragraph> <Paragraph position="3"> b. Hannah likes beetles. She also likes caterpillars.</Paragraph> <Paragraph position="4"> c. Hannah likes beetles. Thomas hates them.</Paragraph> <Paragraph position="5"> (2) is Priist's list construction rule. It is intended to capture the idea that a list can be constructed out of two DCUs, combined by means of connectives such as and and or. The categories in Priist's rules have features associated with them. In (2) these features are sere (the unresolved semantic interpretation of the category), consem (the contextually resolved semantic interpretation), and schema (the semantic information that is common between the daughter categories).</Paragraph> <Paragraph position="6"> (2) list \[sere: el T~ ((Cl C/'$2) RS2),</Paragraph> <Paragraph position="8"> Conditions: C1 $2 is a characteristic generalization of C1 and S~; R E {and, or .... }.</Paragraph> <Paragraph position="9"> Priist calls the operation used to calculate the value for schema the most specific common denominator (MSCD, indicated by the symbol C/). The MSCD of C1 and $2 is defined as the most specific generalization of C1 that can unify with 5'2. It is essential that the result should be contentful to a degree that confirms that the list structure is an appropriate analysis, and to this end Pr/ist imposes the condition that the value of schema should be a characteristic generalization of the information contributed by the two daughters. There is no formal definition of this notion; it would require knowledge from many sources to determine whether sufficient informativeness had been achieved. However, assuming that this condition is met, Priist uses the common information as a source for resolution of underspecified elements in the second daughter by encoding as the value of the second daughter's consem the unification of the result of MSCD with its pre-resolved semantics (the formula ((Ca / $2) Iq $2)). So in Priist's rule the MSCD operation plays two distinct roles, first as a test for parallelism (as the value of the mother's schema) and second as a basis for resolution (in the composite operation which is the value of the second daughter's consem). There are certain problems with MSCD which we claim stem from this attempt to use one operation for two purposes, and our primary concern is to find alternative means of achieving Prfist's intended analysis.</Paragraph> </Section> <Section position="5" start_page="17" end_page="21" type="metho"> <SectionTitle> 2 An ALE Discourse Grammar </SectionTitle> <Paragraph position="0"> For our initial exploration into using ALE for discourse grammars we have developed a small discourse grammar whose lexical items are complete sentences (to circumvent the need for a sentence grammar) and which represents the semantic content of sentences using feature structures of type event whose sub-types are indicated in the following part of the type hierarchy:</Paragraph> <Paragraph position="2"> plus_patient prop-art emot-att action believe assume like hate kick catch In addition we have a very simplified semantics of noun phrases where we encode them as of type entity with the subtypes indicated below:</Paragraph> <Section position="1" start_page="17" end_page="18" type="sub_section"> <SectionTitle> 2.1 Calculating Common Ground </SectionTitle> <Paragraph position="0"> The SCHEMA feature encodes the information that is common between daughter Dcus and Prtist uses MSCD to calculate this information. A feature-structural definition of MSCD would return as a result the most specific feature structure which is at least as general as its first argument but which is also unifiable with its second argument. For the example in (lc), the MSCD operation would be given the two arguments in (5a) and (5d), and (6) would be the result.</Paragraph> <Paragraph position="1"> We can contrast the MSCD operation with an operation which is more commonly discussed in the context of feature-based unification systems, namely generalization. This takes two feature-structures as input and returns a feature structure which represents the common information in them. Unlike MSCD, generalization is not asymmetric, i.e. the order in which the arguments are presented does not affect the result. The generalization of (5a) and (5d) is shown in (7).</Paragraph> <Paragraph position="3"> It can be seen from this example that the MSCD result contains more information than the generalization result. Informally we can say that it seems to reflect the common information between the two inputs after the parallelism-dependent ana- phor in the second sentence has been resolved. The reason it is safe to use MSCD in this context is precisely because its use in a list structure guarantees that the pronoun in the second sentence will be resolved to beetle. In fact the result of MSCD in this case is exactly the result we would get if we were to perform the generalization of the resolved sentences and, as a representation of what the two have in common, it does seem that this is more desirable than the generalization of the pre-resolved forms.</Paragraph> <Paragraph position="4"> If we turn to other examples, however, we discover that MSCD does not always give the best results.</Paragraph> <Paragraph position="5"> The discourse in (8) must receive a constituent structure where the second and third clauses are combined to form a contrast pair and then this contrast pair combines with the first sentence to form a list. (Prfist has a separate rule to build contrast pairs but the use of MSCD is the same as in the list rule.) (8) Hannah likes ants. Thomas likes bees but Jessy hates them.</Paragraph> <Paragraph position="6"> The tree in (9) demonstrates the required structure and also shows on the mother and intermediate nodes what the results of MSCD would be. As we can see, where elements of the first argument of MSCD are more specific than the corresponding elements in the second, then the more specific one occurs in the result. Here, this has the effect that the structure \[like, AGENT hannah, PATIENT insect \] is somehow claimed to be common ground between all three constituents even though this is clearly not the case.</Paragraph> <Paragraph position="7"> Our solution to this problem is to dispense with the MSCD operation and to use generalization instead. However, we do propose that generalization should take inputs whose parallelism dependent anaphors have already been resolved. 1 In the case of the combination of (5a) and (5d), this will give 1As described in the next section, we use priority union to resolve these anaphors in both lists and con- trasts. The use of generalization as a step towards checking that there is sufficient common ground is subsequent to the use of priority ration as the resolution mechanism.</Paragraph> <Paragraph position="8"> exactly the same result as MSCD gave (i.e. (6)), but for the example in (8) we will get different results, as the tree in (10) shows. (Notice that the representation of the third sentence is one where the anaphor is resolved.) The resulting generalization, \[emot_att, AGENT human, PATIENT insect\], is a much more plausible representation of the common information between the three DCUs than the results of MSCD.</Paragraph> </Section> <Section position="2" start_page="18" end_page="19" type="sub_section"> <SectionTitle> 2.2 Resolution of Parallel Anaphors </SectionTitle> <Paragraph position="0"> We have said that MSCD plays two roles in Pr/ist's rules and we have shown how its function in calculating the value of SCHEMA can be better served by using the generalization operation instead. We turn now to the composite operation indicated in (2) by the formula ((C, /S~)NS2). This composite operation calculates MSCD and then unifies it back in with the second of its arguments in order to resolve any parallelism-dependent anaphors that might occur in the second DCU. In the discussion that follows, we will refer to the first DcU in the list rule as the source and to the second DCU as the target (because it contains a parallelism-dependent anaphor which is the target of our attempt to resolve that anaphor).</Paragraph> <Paragraph position="1"> In our ALE implementation we replace Pr/ist's composite operation by an operation which has occasionally been proposed as an addition to feature-based unification systems and which is usually referred to either as default unification or as priority union. 2 Assumptions about the exact definition of this operation vary but an intuitive description of it is that it is an operation which takes two feature structures and produces a result which is a merge of the information in the two inputs. However, the information in one of the feature structures is &quot;strict&quot; and cannot be lost or overridden while the information in the other is defensible. The operation is a kind of union where the information in the strict structure takes priority over that in the ~See, for example, Bouma (1990), Calder (1990), Carpenter (1994), Kaplan (1987).</Paragraph> <Paragraph position="2"> default structure, hence our preference to refer to it by the name priority union. Below we demonstrate the results of priority union for the examples in (la)-(lc). Note that the target is the strict structure and the source is the defeasible one.</Paragraph> <Paragraph position="3"> For these examples priority union gives us exactly the same results as Priist's composite operation.</Paragraph> <Paragraph position="4"> We use a definition of priority union provided by Carpenter (1994) (although note that his name for the operation is &quot;credulous default unification&quot;). It is discussed in more detail in Section 3. The priority union of a target T and a source S is defined as a two step process: first calculate a maximal feature structure S' such that S' E S, and then unify the new feature structure with T.</Paragraph> <Paragraph position="5"> This is very similar to PriJst's composite operation but there is a significant difference, however. For Priist there is a requirement that there should always be a unique MSCD since he also uses MSCD to calculate the common ground as a test for parallelism and there must only be one result for that purpose. By contrast, we have taken Carpenter's definition of credulous default unification and this can return more than one result. We have strong reasons for choosing this definition even though Carpenter does define a &quot;skeptical default unification&quot; operation which returns only one result. Our reasons for preferring the credulous version arise from examples of vP-ellipsis which exhibit an ambiguity whereby both a &quot;strict&quot; and a &quot;sloppy&quot; reading are possible. For example, the second sentence in (14) has two possible readings which can be glossed as &quot;Hannah likes Jessy's brother&quot; (the strict reading) and &quot;Hannah likes her own brother&quot; (the sloppy reading).</Paragraph> <Paragraph position="6"> (14) Jessy likes her brother. So does Hannah.</Paragraph> <Paragraph position="7"> The situations where the credulous version of the operation will return more than one result arise from structure sharing in the defeasible feature structure and it turns out that these are exactly the places where we would need to get more than one result in order to get the strict/sloppy ambiguities. We illustrate below: Here priority union returns two results, one where the structure-sharing information in the source has been preserved and one where it has not. As the example demonstrates, this gives the two readings required. By contrast, Carpenter's skeptical default unification operation and Priist's composite operation return only one result.</Paragraph> </Section> <Section position="3" start_page="19" end_page="19" type="sub_section"> <SectionTitle> 2.3 Higher Order Unification </SectionTitle> <Paragraph position="0"> There are similarities between our implementation of Prfist's grammar and the account of vP-ellipsis described by Dalrymple, Shieber and Pereira (1991) (henceforth DSP). DSP gives an equational characterization of the problem of vp-ellipsis where the interpretation of the target phrase follows from an initial step of solving an equation with respect to the source phrase. If a function can be found such that applying that function to the source subject results in the source interpretation, then an application of that function to the target subject will yield the resolved interpretation for the target. The method for solving such equations is &quot;higher order unification&quot;. (16) shows all the components of the interpretation of the example in (11).</Paragraph> <Paragraph position="2"> A prerequisite to the DSP procedure is the establishment of parallelism between source and target and the identification of parallel subparts. For example, for (16) it is necessary both that the two clauses Hannah likes beetles and So does Thomas should be parallel and that the element hannah should be identified as a parallel element. DSP indicate parallel elements in the source by means of underlines as shown in (16). An underlined element in the source is termed a 'primary occurrence' and DSP place a constraint on solutions to equations requiring that primary occurrences be abstracted. Without the identification of hannah as a primary occurrence in (16), other equations deriving from the source might be possible, for ex-</Paragraph> <Paragraph position="4"> The DSP analysis of our strict/sloppy example in (14) is shown in (18). The ambiguity follows from the fact that there are two possible solutions to the equation on the source: the first solution involves abstraction of just the primary occurrence ofjessy, while the second solution involves abstraction of both the primary and the secondary occurrences.</Paragraph> <Paragraph position="5"> When applied to the target these solutions yield the two different interpretations: likes her brother. So does Hannah.</Paragraph> <Paragraph position="7"> DSP claim that a significant attribute of their account is that they can provide the two readings in strict/sloppy ambiguities without having to postulate ambiguity in the source. They claim this as a virtue which is matched by few other accounts of vP-ellipsis. We have shown here, however, that an account which uses priority union also has no need to treat the source as ambiguous.</Paragraph> <Paragraph position="8"> Our results and DSP's also converge where the treatment of cascaded ellipsis is concerned. For the example in (19) both accounts find six readings although two of these are either extremely implausible or even impossible.</Paragraph> <Paragraph position="9"> (19) John revised his paper before the teacher did, and Bill did too.</Paragraph> <Paragraph position="10"> DSP consider ways of reducing the number of readings and, similarly, we are currently exploring a potential solution whereby some of the re-entrancies in the source are required to be transmitted to the result of priority union.</Paragraph> <Paragraph position="11"> There are also similarities between our account and the DSP account with respect to the establishment of parallelism. In the DSP analysis the determination of parallelism is separate from and a prerequisite to the resolution of ellipsis. However, they do not actually formulate how parallelism is to be determined. In our modification of Prfist's account we have taken the same step as DSP in that we separate out the part of the feature structure used to determine parallelism from the part used to resolve ellipsis. In the general spirit of Priist's analysis, however, we have taken one step further down the line towards determining parallelism by postulating that calculating the generalization of the source and target is a first step towards showing that parallelism exists.</Paragraph> <Paragraph position="12"> The further condition that Prfist imposes, that the common ground should be a characteristic generalization, would conclude the establishment of parallelism. We are currently not able to define the notion of characteristic generalization, so like DSP we do not have enough in our theory to fully implement the parallelism requirement. In contrast to the DSP account, however, our feature structural approach does not involve us having to explicitly pair up the component parts of source and target, nor does it require us to distinguish primary from secondary occurrences.</Paragraph> </Section> <Section position="4" start_page="19" end_page="21" type="sub_section"> <SectionTitle> 2.4 Parallelism </SectionTitle> <Paragraph position="0"> In the DSP approach to vP-ellipsis and in our approach too, the emphasis has been on semantic parallelism. It has often been pointed out, however, that there can be an additional requirement of syntactic parallelism (see for example, Kehler 1993 and Asher 1993). Kehler (1993) provides a useful discussion of the issue and argues convincingly that whether syntactic parallelism is required depends on the coherence relation involved. As the examples in (20) and (21) demonstrate, semantic parallelism is sufficient to establish a relation like contrast but it is not sufficient for building a co- null herent list.</Paragraph> <Paragraph position="1"> (20) The problem was looked into by John, but no-one else did.</Paragraph> <Paragraph position="2"> (21) *This problem was looked into by John, and Bill did too.</Paragraph> <Paragraph position="3"> For a list to be well-formed both syntactic and semantic parallelism are required: (22) John looked into this problem, and Bill did too.</Paragraph> <Paragraph position="4"> In the light of Kehler's claims, it would seem that a more far-reaching implementation of our priority union account would need to specify how the constraint of syntactic parallelism might be implemented for those constructions which require it. An nPSG-style sign, containing as it does all types of linguistic information within the same feature structure, would lend itself well to an account of syntactic parallelism. If we consider that the DTRS feature in the sign for the source clause contains the entire parse tree including the node for the vP which is the syntactic antecedent, then ways to bring together the source vP and the target begin to suggest themselves. We have at our disposal both unification to achieve re-entrancy and the option to use priority union over syntactic subparts of the sign. In the light of this, we are confident that it would be possible to articulate a more elaborate account of vp-ellipis within our framework and that priority union would remain the operation of choice to achieve the resolution.</Paragraph> </Section> </Section> <Section position="6" start_page="21" end_page="23" type="metho"> <SectionTitle> 3 Extensions to ALE </SectionTitle> <Paragraph position="0"> In the previous sections we showed that Prfist's MSCD operation would more appropriately be replaced by the related operations of generalization and priority union. We have added generalization and priority union to the ALE system and in this section we discuss our implementation. We have provided the new operations as a complement to the definite clause component of ALE. We chose this route because we wanted to give the grammar writer explicit control of the point at which the operations were invoked. ALE adopts a simple eROLOG-like execution strategy rather than the more sophisticated control schemes of systems like CUF and TFS (Manandhar 1993). In principle it might be preferable to allow the very general deduction strategies which these other systems support, since they have the potential to support a more declarative style of grammar-writing. Unfortunately, priority union is a non-monotonic operation, and the consequences of embedding such operations in a system providing for flexible execution strategies are largely unexplored. At least at the outset it seems preferable to work within a framework in which the grammar writer is required to take some of the responsibility for the order in which operations are carried out. Ultimately we would hope that much of this load could be taken by the system, but as a tool for exploration ALE certainly suffices.</Paragraph> <Section position="1" start_page="21" end_page="22" type="sub_section"> <SectionTitle> 3.1 Priority Union in ALE </SectionTitle> <Paragraph position="0"> We use the following definition of priority union, based on Carpenter's definition of credulous default unification: (23) punion(T,S) = {unify(T,S') IS' K S is maximal such that unify(T,S') is defined} punion(T,S) computes the priority union oft (target; the strict feature structure) with S (source; the defeasible feature structure). This definition relies on Moshier's (1988) definition of atomic feature structures, and on the technical result that any feature structure can be decomposed into a unification of a unique set of atomic feature structures. Our implementation is a simple proceduralization of Carpenter's declarative definition. First we decompose the default feature structure into a set of atomic feature structures, then we search for the maximal subsets required by the definition.</Paragraph> <Paragraph position="1"> We illustrate our implementation of priority union in ALE with the example in (15): Source is the default input, and Target is the strict input. The hierarchy we assume is the same as shown in (3) and (4). Information about how features are associated with types is as follows: * The type agentive introduces the feature AGENT with range type human.</Paragraph> <Paragraph position="2"> tures.</Paragraph> <Paragraph position="3"> In order to show the decomposition into atomic feature structures we need a notation to represent paths and types. We show paths like this: PATIENTIBROTHER-OF and in order to stipulate that the PATIENT feature leads to a structure of type brother, we include type information in this way: (PATIENW/brother)\[(BROTHERof~human). We introduce a special feature (*) to allow specification of the top level type of the structure. The structures in (15) decompose into the following atomic components.</Paragraph> <Paragraph position="4"> (24) Default input:</Paragraph> <Paragraph position="6"> Given the type hierarchy the expressions above expand to the following typed feature structures: We can now carry out the following steps in order to generate the priority union.</Paragraph> <Paragraph position="7"> 1. Add (94) to the strict input. It cannot conflict. 2. Note that it is impossible to add (D1) to the strict input.</Paragraph> <Paragraph position="8"> 3. Non-deterministically add either (92) or (93) to the strict input.</Paragraph> <Paragraph position="9"> 4. Note that the results are maximal in each case because it is impossible to add both (D2) and (D3) without causing a clash between the disjoint atomic types hannah and jessy. 5. Assemble the results into feature structures. If we have added (D3) the result will be (26) and if we have added (D2) the result will be (27). In order to make this step-by-step description into an algorithm we have used a breadth-first search routine with the property that the largest sets are generated first. We collect answers in the order in which the search comes upon them and carry out subsumption checks to ensure that all the answers which will be returned are maximal. These checks reduce to checks on subset inclusion, which can be reasonably efficient with suitable set representations. Consistency checking is straightforward because the ALE system manages type information in a manner which is largely transparent to the user. Unification of ALE terms is defined in such a way that if adding a feature to a term results in a term of a new type, then the representation of the structure is specialized to reflect this. Since priority union is non-deterministic we will finish with a set of maximal consistent subsets. Each of these subsets can be converted directly into ALE terms using ALE's built-in predicate add_to/5. The resulting set of ALE terms is the (disjunctive) result of priority union.</Paragraph> <Paragraph position="10"> In general we expect priority union to be a computationally expensive operation, since we cannot exclude pathological cases in which the system has to search an exponential number of subsets in the search for the maximal consistent elements which are required. In the light of this it is fortunate that our current discourse grammars do not require frequent use of priority union. Because of the inherent complexity of the task we have favoured correctness and clarity at the possible expense of efficiency. Once it becomes established that priority union is a useful operation we can begin to explore the possibilities for faster implementations. null</Paragraph> </Section> <Section position="2" start_page="22" end_page="23" type="sub_section"> <SectionTitle> 3.2 Generalization in ALE </SectionTitle> <Paragraph position="0"> The abstract definition of generalization stipulates that the generalization of two categories is the largest category which subsumes both of them. Moshier (1988) has shown that generalization can be defined as the intersection of sets of atomic feature structures. In the previous section we outlined how an ALE term can be broken up into atomic feature structures. All that is now required is the set intersection operation with the addition that we also need to cater for the possibility that atomic types may have a consistent generalization.</Paragraph> <Paragraph position="1"> 1. For P and Q complex feature structures Gen(P,Q) =~! {Path: C I Path: A E P and Path : B E Q } where C is the most specific type which subsumes both A and B.</Paragraph> <Paragraph position="2"> 2. For A and B atomic types Gen(A, B) =dr C where C is the most specific type which subsumes both A and B.</Paragraph> <Paragraph position="3"> In ALE there is always a unique type for the generalization. We have made a small extension to the ALE compiler to generate a table of type generalizations to assist in the (relatively) efficient computation of generalization. To illustrate, we show how the generalization of the two feature structures in (28) and (29) is calculated.</Paragraph> <Paragraph position="4"> These have only the AGENT path in common although with different values and therefore the generalization is the feature structure corresponding to this path but with the generalization of the atomic types hannah and jessy as value:</Paragraph> </Section> </Section> class="xml-element"></Paper>