File size: 52,270 Bytes
6fa4bc9 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 | {
"paper_id": "P91-1010",
"header": {
"generated_with": "S2ORC 1.0.0",
"date_generated": "2023-01-19T09:03:21.628416Z"
},
"title": "TYPE-RAISING AND DIRECTIONALITY IN COMBINATORY GRAMMAR*",
"authors": [
{
"first": "Mark",
"middle": [],
"last": "Steedman",
"suffix": "",
"affiliation": {
"laboratory": "",
"institution": "University of Pennsylvania",
"location": {
"addrLine": "200 South 33rd Street Philadelphia PA",
"postCode": "19104-6389",
"country": "USA"
}
},
"email": "steedman@cis@edu"
}
],
"year": "",
"venue": null,
"identifiers": {},
"abstract": "The form of rules in \u00a2ombinatory categorial grammars (CCG) is constrained by three principles, called \"adjacency\", \"consistency\" and \"inheritance\". These principles have been claimed elsewhere to constrain the combinatory rules of composition and type raising in such a way as to make certain linguistic universals concerning word order under coordination follow immediately. The present paper shows that the three principles have a natural expression in a unification-based interpretation of CCG in which directional information is an attribute of the arguments of functions grounded in string position. The universals can thereby be derived as consequences of elementary assumptions. Some desirable results for grammars and parsers follow, concerning type-raising rules. PRELIMINARIES In Categorial Grammar (CG), elements like verbs are associated with a syntactic \"category\", which identifies their functional type. I shall use a notation in which the argument or domain category always appears to the right of the slash, and the result or range category to the left. A forward slash / means that the argument in question must appear on the right, while a backward slash \\ means it must appear on the left.",
"pdf_parse": {
"paper_id": "P91-1010",
"_pdf_hash": "",
"abstract": [
{
"text": "The form of rules in \u00a2ombinatory categorial grammars (CCG) is constrained by three principles, called \"adjacency\", \"consistency\" and \"inheritance\". These principles have been claimed elsewhere to constrain the combinatory rules of composition and type raising in such a way as to make certain linguistic universals concerning word order under coordination follow immediately. The present paper shows that the three principles have a natural expression in a unification-based interpretation of CCG in which directional information is an attribute of the arguments of functions grounded in string position. The universals can thereby be derived as consequences of elementary assumptions. Some desirable results for grammars and parsers follow, concerning type-raising rules. PRELIMINARIES In Categorial Grammar (CG), elements like verbs are associated with a syntactic \"category\", which identifies their functional type. I shall use a notation in which the argument or domain category always appears to the right of the slash, and the result or range category to the left. A forward slash / means that the argument in question must appear on the right, while a backward slash \\ means it must appear on the left.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "Abstract",
"sec_num": null
}
],
"body_text": [
{
"text": "of combination in which X and Y are abbreviations for more complex objects which combine via unification. They allow context-free derivations like the following (the application of rules is indicated by indices >, < on the underlines: The derivation can be assumed to build a compositional interpretation, (enjoy' musicals') mary', say.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "Coordination can be included in CG via the following rule, allowing constituents of like type to conjoin to yield a single constituent of the same type: (4) X conj X =~ X ",
"cite_spans": [
{
"start": 153,
"end": 156,
"text": "(4)",
"ref_id": "BIBREF3"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
},
{
"text": "The rest of the derivation is exactly as in (3) .",
"cite_spans": [
{
"start": 44,
"end": 47,
"text": "(3)",
"ref_id": "BIBREF2"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "In order to allow coordination of contiguous strings that do not constitute constituents, CCG allows certain operations on functions related to Curry's combinatots [1] . Functions may compose, as well as apply, under rules like the following:",
"cite_spans": [
{
"start": 164,
"end": 167,
"text": "[1]",
"ref_id": "BIBREF0"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(6) Forward Composition: X/Y Y/Z ~B X/Z (>B)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The rule corresponds to Curry's eombinator B, as the subscripted arrow indicates. It allows sentences like Mary admires, and may enjoy, musicals to be accepted, via the functional composition of two verbs (indexed as >B), to yield a composite of the same category as a transitive verb. Crucially, composition also yields the appropriate interpretation for the composite verb may prefer in this sentence (the rest of the derivation is as in (3)): (s\\~)/~P CCG also allows type-raising rules, related to the combinator T, which turn arguments into functions over functions-over-such-arguments. These rules allow arguments to compose, and thereby lake part in coordinations like I dislike, and Mary enjoys, musicals. They too have an invariant compositional semantics which ensures that the result has an appropriate interpretation. For example, the following rule allows such conjuncts to form as below (again, the remainder of the derivation is omitted): (8) Subject ~pe-raising: This apparatus has been applied to a wide variety of phenomena of long-range dependency and coordinate structure (cf. [2] , [5] , [6] ). 1 For example, Dowty proposed to account for the notorious \"non-constituent\" coordination in (10) by adding two rules that are simply the backward mitre-image versions of the composition and type raising rules already given (they are indicated in the derivation by <B and <T). 2 This is a welcome result: not only do we capture a construction that has been resistant to other formalisms. We also satisfy a prediction of the theory, for the two backward rules arc clearly expected once we have chosen to introduce their mirror image originals. The earlier papers show that, provided type raising is limited to the two \"order preserving\" varieties exemplified in these examples, the above reduction is the only one permitted by the lexicon of English. A number of related cross-linguistic regularities in the dependency of gapping upon basic word order follow ( [2] , [6] ). The construction also strongly suggests that all NPs (etc.) should be considered as type raised, preferably I One further class of rules, corresponding to the combinator S, has been proposed. This combinator is not discussed here, but all the present results transfer to tho6e rules as well.",
"cite_spans": [
{
"start": 1097,
"end": 1100,
"text": "[2]",
"ref_id": "BIBREF1"
},
{
"start": 1103,
"end": 1106,
"text": "[5]",
"ref_id": "BIBREF4"
},
{
"start": 1109,
"end": 1112,
"text": "[6]",
"ref_id": "BIBREF5"
},
{
"start": 1976,
"end": 1979,
"text": "[2]",
"ref_id": "BIBREF1"
},
{
"start": 1982,
"end": 1985,
"text": "[6]",
"ref_id": "BIBREF5"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "EQUATION",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [
{
"start": 0,
"end": 8,
"text": "EQUATION",
"ref_id": "EQREF",
"raw_str": "NP : y ~T S/(S\\NP) (> T)",
"eq_num": "(9)"
}
],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "2This and other long examples have been \"flmted\" to later positions in the text.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "in the lexicon, and that categories like NP should not reduce at all. However, this last proposal seems tc implies a puzzling extra ambiguity in the lexicon, and for the moment we will continue to view type-raising as a syntactic rule.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The universal claim depends upon type-raising being limited to the following schemata, which do not of themselves induce new constituent orders:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(11) x =~T T/if\\X) X :::}T T\\(T/X)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "If the following patterns (which allow constituent orders that are not otherwise permitted) were allowed, the regularity would be unexplained, and without further restrictions, grammars would collapse into free order:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(12) X ::",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": ":}T T/(T/X) X ::~T T\\(T\\X)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "But what are the principles that limit combinatory rules of grammar, to include (11) and exclude (12)?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The earlier papers claim that all CCG rules must conform to three principles. The first is called the Principle of Adjacency [5, pA05] , and says that rules may only apply to string-adjacent non-empty categories. It amounts to the assumption that combinatops will do the job. The second is called the Principle of Directional Consistency. Informally stated, it says that rules may not override the directionality on the \"cancelling\" Y category in the combination. For example, the following rule is excluded:",
"cite_spans": [
{
"start": 125,
"end": 134,
"text": "[5, pA05]",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(13) \u2022 X\\Y Y => X",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The third is the Principle of Directional Inheritance, which says that the directionality of any argument in the result of a combinatory rule must be the same as the directionality on the corresponding argument(s) in the original functions. For example, the following composition rule is excluded:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(14) * X/Y Y/Z => X\\Z",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "However, rules like the following are permitted:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(15) Y/Z X\\Y => X/Z (<Bx)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "This rule (which is not a theorem in the Lambek calculus) is used in [5] to account for examples like I shall buy today and read tomorrow, the collected works of Proust, the crucial combination being the following:",
"cite_spans": [
{
"start": 69,
"end": 72,
"text": "[5]",
"ref_id": "BIBREF4"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "(16) ... read tomorxow ... vP/m, vP\\vP ............ <Bx VP/NP",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The principles of consistency and inheritance amount to the simple statement that combinatory rules may not contradict the directionality specified in the lexicon. But how is this observation to be formalised, and how does it bear on the type-raising rules? The next section answers these questions by proposing an interpretation, grounded in string positions, for the symbols / and \\ in CCG. The notation will temporarily become rather heavy going, so it should be clearly understood that this is not a proposal for a new CCG notation. It is a semantics for the metagrammar of the old CCG notation.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "(s\\m')/m,",
"sec_num": null
},
{
"text": "The fact that directionality of arguments is inherited under combinatory rules, under the third of the principles, strongly suggests that it is a property of arguments themselves, just like their eategorial type, NP or whatever, as in the work of Zeevat et al. [8] [9] . However, the feature in question will here be grounded in a different representation, with significantly different consequences, as follows. The basic form of a combinatory rule under the principle of adjacency is a fl ~ ~,. However, this notation leaves the linear order of ot and fl implicit. We therefore temporarily expand the notation, replacing categories like NP by 4-tuples, of the form {e~, DPa, L~, Ra}, comprising: a) a type such as NP; b) a Distinguished Position, which we will come to in a minute; c) a Leftend position; and d) a Right-end position. The Principle of Adjacency finds expression in the fact that all legal combinatory rules must have the the form in (17), in which the right-end of ~ is the same as the left-end of r: We will call the position P2, to which the two categories are adjacent, the juncture.",
"cite_spans": [
{
"start": 261,
"end": 264,
"text": "[8]",
"ref_id": "BIBREF7"
},
{
"start": 265,
"end": 268,
"text": "[9]",
"ref_id": "BIBREF8"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "The Distinguished Position of a category is simply the one of its two ends that coincides with the juncture when it is the \"'cancelling\" term Y. A rightward combining function, such as the transitive verb enjoy, specifies the distinguished position of its argument (here underlined for salience) as being that argument's left-end. So this category is written in full as in (18)a, using a non-directional slash/. The notation in (a) is rather overwhelming. When positional features are of no immediate relevance in such categories, they will be suppressed. For example, when we are thinking of such a function as a function, rather than as an argument, we will write it as in (18)b, where VP stands for {VP, DFVp, Lw,, Rvp}, and the distinguished position of the verb is omitted. It is important to note that while the binding of the NP argument's Distinguished Position to its left hand end L,p means that enjoy is a rightward function, the distinguished position is not bound to the right hand end of the verb, t~verb. It follows that the verb can potentially combine with an argument elsewhere, just so long as it is to the right. This property was crucial to the earlier analysis of heavy NP shift. Coupled with the parallel independence in the position of the result from the position of the verb, it is the point at which CCG parts company with the directional Lambek calculus, as we shall see below.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "In the expanded notation the rule of forward application is written as in (19). The fact that the distinguisbed position must be one of the two ends of an argument category, coupled with the requirement of the principle of Adjacency, means that only the two order-preserving instances of functional application shown in (2) can exist, and only consistent categories can unify with those rules.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "A combination under this rule proceeds as follows. Consider example (20), the VP enjoy musicals. The derivation continues as follows. First the positional variables of the categories are bound by the positions in which the words occur in the siring, as in (21), which in the first place we will represent explicitly, as numbered string positions, s Next the combinatory rule (19) applies, to unify the argument term of the function with the real argument, binding the remaining positional variables including the distinguished position, as in (22) and (23). At the point when the combinatory rule applies, the constraint implicit in the distinguished position must actually hold. That is, the distinguished position must be adjacent to the functor.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "Thus the Consistency property of combinatory rules follows from the principle of Adjacency, embodied in the fact that all such rules identify the distinguished position of the argument terms with the juncture P2, the point to which the two combinands are adjacent, as in the application example (19).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "The principle of Inheritance also follows directly from these assumptions. The fact that rules correspond to combinators like composition forces directionality to be inherited, like any other property of an argument such as being an NP. It follows that only instances of the two very general rules of composition shown in (24) are allowed, as a consequence of the three Principles. To conform to the principle of consistency, it is necessary that L~ and /~, the ends of the cancelling category Y, be distinct positions -that is, that Y not be coerced to the empty string. This condition is implicit in the Principle of Adjacency (see above), although in the notation of the appendix it has to be explicitly imposed. These schemata permit only the four instances of the rules of composition proposed in [5] [6] , given in (25) in the basic CCG notation. \"Crossed\" rules like (15) are still allowed Coecause of the non-identity noted in the discussion of (18) between the distinguished position of arguments of functions and the position of the function itself). They are distinguished from the corresponding non-crossing rules by further specifying DP~, the distinguished position on Z. However, no rule violating the Principle of Inheritance, like (14), is allowed: such a rule would require a different distinguished position on the two Zs, and would therefore not be functional composition at all. This is a desirable result: the example (16) and the earlier papers show that the non-order-preserving instances (b, d) are required for the grammar of English and Dutch.",
"cite_spans": [
{
"start": 802,
"end": 805,
"text": "[5]",
"ref_id": "BIBREF4"
},
{
"start": 806,
"end": 809,
"text": "[6]",
"ref_id": "BIBREF5"
}
],
"ref_spans": [],
"eq_spans": [],
"section": "DIRECTIONALITY IN CCG",
"sec_num": null
},
{
"text": "In configurational languages like English they must of course be carefully restricted as to the categories that may unify with Y.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "The implications of the present formalism for the type-raising rules are less obvious. Type raising rules are unary, and probably lexical, so the principle of adjacency does not apply. However, we noted earlier that we only want the order-preserving instances (11), in which the directionality of the raised category is the reverse of that of its argument. But how can this reversal be anything but an arbitrary property?",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "Because the directionality constraints are grounded out in string positions, the distinguished position of the subject argument of a predicate walks -that is, the right-hand edge of that subject -is equivalent to the distinguished position of the predicate that constitutes the argument of an order-preserving raised subject Gilbert that is, the left-hand edge of that predicate. It follows that both of the order-preserving rules are instances of the single rule (26) in the extended notation: The crucial property of this rule, which forces its instances to be order-preserving, is that the distinguished position variable D Parg on the argument of the predicate in the raised category is the same as that on the argument of the raised category itself. (l'he two distinguished positions are underlined in (26)). Of course, the position is unspecified at the time of applying the rule, and is simply represented as an unbound unification variable with an arbitrary mnemonic identifier. However, when the category combines with a predicate, this variable will be bound by the directionality specified in the predicate itself. Since this condition will be transmitted to the raised category, it will have to coincide with the juncture of the combination. Combination of the categories in the non-grammatical order will therefore fail, just as if the original categories were combining without the mediation of type-raising.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "Consider the following example. Under the above rule, the categories of the words in the sentence Gilbert walks are as shown in (27), before binding. Binding of string positional variables yields the categories in (28). The combinatory rule of forward application (19) applies as in example (29), binding further variables by unification. In particular, DP 9, Prop, DPw, and P2, are all bound to the juncture position 2, as in (30). By contrast, the same categories in the opposite linear order fail to unify with any combinatory rule. In particular, the backward application rule fails, as in (31). (Combination is blocked because 2 cannot unify with 3).",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "On the assumption implicit in (26), the only permitted instances of type raising are the two rules given earlier as (11). The earlier results concerning wordorder universals under coordination are therefore captured. Moreover, we can now think of these two rules as a single underspecified order-preserving rule directly corresponding to (26), which we might write less long-windediy as follows, augmenting the original simplest notation with a non-directional slash: (33) The Order-preserving Type-raising Rule:",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "X ~ TI(TIX) (T)",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "The category that results from this rule can combine in either direction, but will always preserve order. Such a property is extremely desirable in a language like English, whose verb requires some arguments to the right, and some to the left, but whose NPs do not bear case. The general raised category can combine in both directions, but will still preserve word order. It thus eliminates what was earlier noted as a worrying extra degree of categorial ambiguity. The way is now clear to incorporate type raising directly into the lexicon, substituting categories of the form T I(TIX), where X is a category like NP or PP, directly into the lexicon in place of the basic categories, or (more readably, but less efficiently), to keep the basic categories and the rule (33), and exclude the base categories from all combination.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "The related proposal of Zeevat et al. [8] , [9] also has the property of allowing a single lexical raised category for the English NP. However, because of the way in which the directional constraints are here grounded in relative string position, rather than being primitive to the system, the present proposal avoids certain difficulties in the earlier treatment. Zeevat's type-raised categories are actually order-changing, and require the lexical category for the English predicate to be S/NP instead of S\\NP. (Cf. [9, It is important to be clear that, while the order preserving constraint is very simply imposed, it is nevertheless an additional stipulation, imposed by the form of the type raising rule (26). We could have used a unique variable, DPpr,a say, in the crucial position in (26), unrelated to the positional condition DP~r9 on the argument of the predicate itself, to define the distinguished position of the predicate argument of the raised category, as in example (32). However, this tactic would yield a completely unconstrained type raising rule, whose result category could not merely be substituted throughout the lexicon for ground categories like NP without grammatical collapse. (Such categories immediately induce totally free word-order, for example permitting (31) on the English lexicon). It seems likely that type raising is universally confined to the order-preserving kind, and that the sources of so-called free word order lie elsewhere. Such a constraint can therefore be understood in terms of the present proposal simply as a requirement for the lexicon itself to be consistent. It should also be observed that a uniformly order-changing category of the kind proposed by Zeevat et al. is not possible under this theory.",
"cite_spans": [
{
"start": 38,
"end": 41,
"text": "[8]",
"ref_id": "BIBREF7"
},
{
"start": 44,
"end": 47,
"text": "[9]",
"ref_id": "BIBREF8"
},
{
"start": 518,
"end": 521,
"text": "[9,",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "The above argument translates directly into unification-based frameworks such as PATR or Prolog. A small Prolog program, shown in an appendix, can be used to exemplify and check the argument. 4 The program makes no claim to practicality or efficiency as a CCG parser, a question on which the reader is refered to [7] . Purely for explanatory simplicity, it uses type raising as a syntactic rule, rather than as an offline lexical rule. While a few English lexical categories and an English sentence are given by way of illustration, the very general combinatory rules that are included will of course require further constraints if they are not to overgenerate with larger fragments. (For example, >B and >Bx must be disanguished as outlined above, and file latter must be greatly constrained for English.) One very general constraint, excluding all combinations with or into NP, is included in the program, in order to force type-raising and exemplify the way in which further constrained rule-instances may be specified.",
"cite_spans": [
{
"start": 192,
"end": 193,
"text": "4",
"ref_id": "BIBREF3"
},
{
"start": 313,
"end": 316,
"text": "[7]",
"ref_id": "BIBREF6"
}
],
"ref_spans": [],
"eq_spans": [],
"section": ",R.}/{Y, P2,P2,P~},P1,P2} {{Y, P2,P2,P~}/{Z, DPz,Lz,R.},P2,P3) :~ {{X, DPx,L,,,R~,}/{Z, DP.,L.,R.},PI,P3} b. {{Y, P2, Ly, P2}/{Z, DPz, Lz, Rz}, PI, P2} {{X, DPx, L~, R~}/{Y, P2, Lu, P2}, P2, P3} :~ {{X, DPx, Lx,Rz}/{Z, DPz,L,,Rz},PI,P3}",
"sec_num": null
},
{
"text": "We can now safely revert to the original CCG nota-4The program is based on a simple shift-reduce parser/rccogniscr, using \"difference list\"-encoding of string position (el. [41, [31) . tion described in the preliminaries to the paper, modified only by the introduction of the general orderpreserving type raising rule (26), having established the following results. First, the earlier claims concerning word-order universals follow fTom first principles in a unification-based CCG in which directionality is an attribute of arguments, grounded out in string position. The Principles of Consistency and Inheritance follow as theorems, rather than stipulations. A single general-purpose order-preserving type-raised category can be assigned to arguments, simplifying the grammar and the parser.",
"cite_spans": [
{
"start": 173,
"end": 182,
"text": "[41, [31)",
"ref_id": null
}
],
"ref_spans": [],
"eq_spans": [],
"section": "CONCLUSION",
"sec_num": null
},
{
"text": "Declaritivising position like this may seem laborious, but it is a tactic familiar from the DCG literature, from which we shall later borrow the elegant device of encoding such positions implicitly in difference-lists.",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "",
"sec_num": null
}
],
"back_matter": [
{
"text": "~ A Lexical Frasment: parse will bind position (via list-encoding): category(gilbert, cat(np, _, P1, P2)). category(brigitte, cat(np, _, P1, P2)). category(ualks0cat(cat(s ...... )/cat(np,P2,_,P2),_,P3,P4)). category(love, cat(cat(vp ...... )/cat(np,P3,P3,_),_,P1,P2)). category(must,cat(cat(cat(s ...... )/cat(np,P2,_,P2) ...... )/cat(vp,P5,PS,_),_,P3,P4)). category(madly, cat(cat(vp, ..... )/cat(vp,P2,_,P2),_,P3,P4)). ",
"cite_spans": [],
"ref_spans": [],
"eq_spans": [],
"section": "APPENDIX",
"sec_num": null
}
],
"bib_entries": {
"BIBREF0": {
"ref_id": "b0",
"title": "Combinatory Logic",
"authors": [
{
"first": "I-Iaskell",
"middle": [],
"last": "Curry",
"suffix": ""
},
{
"first": "Robert",
"middle": [],
"last": "Feys",
"suffix": ""
}
],
"year": 1958,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Curry, I-Iaskell and Robert Feys: 1958, Combi- natory Logic, North Holland, Amsterdam.",
"links": null
},
"BIBREF1": {
"ref_id": "b1",
"title": "Type raising, functional composition, and non-constituent coordination",
"authors": [
{
"first": "David",
"middle": [],
"last": "Dowry",
"suffix": ""
}
],
"year": 1988,
"venue": "Categorial Grammars and Natural Language Structures",
"volume": "",
"issue": "",
"pages": "153--198",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Dowry, David: 1988, Type raising, functional composition, and non-constituent coordination, in Richard T. Oehrle, E. Bach and D. Wheeler, (eds), Categorial Grammars and Natural Lan- guage Structures, Reidel, Dordrecht, 153-198.",
"links": null
},
"BIBREF2": {
"ref_id": "b2",
"title": "Functor-driven Natural Language Generation with Categorial Unification Grammars",
"authors": [
{
"first": "Dale",
"middle": [],
"last": "Gerdeman",
"suffix": ""
},
{
"first": "Erhard",
"middle": [],
"last": "Hinrichs",
"suffix": ""
}
],
"year": 1990,
"venue": "Proceedings of COLING 90, Helsinld",
"volume": "",
"issue": "",
"pages": "145--150",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Gerdeman, Dale and Hinrichs, Erhard: 1990. Functor-driven Natural Language Generation with Categorial Unification Grammars. Proceedings of COLING 90, Helsinld, 145-150.",
"links": null
},
"BIBREF3": {
"ref_id": "b3",
"title": "Prolog and Natural Language Analysis, CSLIAJniv",
"authors": [
{
"first": "Fernando",
"middle": [],
"last": "Pereira",
"suffix": ""
},
{
"first": "Smart",
"middle": [],
"last": "Shieber",
"suffix": ""
}
],
"year": 1987,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Pereira, Fernando, and Smart Shieber: 1987, Pro- log and Natural Language Analysis, CSLIAJniv. of Chicago Press.",
"links": null
},
"BIBREF4": {
"ref_id": "b4",
"title": "Combinatory grammars and parasitic gaps",
"authors": [
{
"first": "Mark",
"middle": [],
"last": "Steedman",
"suffix": ""
}
],
"year": 1987,
"venue": "Natural Language & Linguistic Theory",
"volume": "5",
"issue": "",
"pages": "403--439",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Steedman, Mark: 1987. Combinatory grammars and parasitic gaps. Natural Language & Linguis- tic Theory, 5, 403-439.",
"links": null
},
"BIBREF5": {
"ref_id": "b5",
"title": "Gapping as Constitutent Coordination",
"authors": [
{
"first": "Mark",
"middle": [],
"last": "Steedman",
"suffix": ""
}
],
"year": 1990,
"venue": "Linguistics and Philosophy",
"volume": "13",
"issue": "",
"pages": "207--263",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Steedman, Mark: 1990, Gapping as Constitu- tent Coordination, Linguistics and Philosophy, 13, 207-263.",
"links": null
},
"BIBREF6": {
"ref_id": "b6",
"title": "Polynomial Time Parsing of Combinatory Categorial Grammars",
"authors": [
{
"first": "K",
"middle": [],
"last": "Vijay-Shartkar",
"suffix": ""
},
{
"first": "David",
"middle": [],
"last": "Weir",
"suffix": ""
}
],
"year": 1990,
"venue": "Proceedings of the 28th Annual Conference of the ACL",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Vijay-Shartkar, K and David Weir: 1990, 'Poly- nomial Time Parsing of Combinatory Categorial Grammars', Proceedings of the 28th Annual Con- ference of the ACL, Pittsburgh, June 1990.",
"links": null
},
"BIBREF7": {
"ref_id": "b7",
"title": "An Introduction to Unification Categorial Grammar",
"authors": [
{
"first": "Hunk",
"middle": [],
"last": "Zeevat",
"suffix": ""
},
{
"first": "Ewan",
"middle": [],
"last": "Klein",
"suffix": ""
},
{
"first": "Jo",
"middle": [],
"last": "Calder",
"suffix": ""
}
],
"year": 1987,
"venue": "Edinburgh Working Papers in Cognitive Science, 1: Categorial Grammar, Unification Grammar, and Parsing",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Zeevat, Hunk, Ewan Klein, and Jo Calder: 1987, 'An Introduction to Unification Categorial Gram- mar', in N. Haddock et al. (eds.), Edinburgh Working Papers in Cognitive Science, 1: Catego- rial Grammar, Unification Grammar, and Pars- ing.",
"links": null
},
"BIBREF8": {
"ref_id": "b8",
"title": "Combining Categorial Grammar and Unification",
"authors": [
{
"first": "Henk",
"middle": [],
"last": "Zeevat",
"suffix": ""
}
],
"year": 1988,
"venue": "",
"volume": "",
"issue": "",
"pages": "",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Zeevat, Henk: 1988, 'Combining Categorial Grammar and Unification', in U. Reyle and C.",
"links": null
},
"BIBREF9": {
"ref_id": "b9",
"title": "Natural Language Parsing and Linguistic Theories",
"authors": [
{
"first": "",
"middle": [],
"last": "Rohrer",
"suffix": ""
}
],
"year": null,
"venue": "",
"volume": "",
"issue": "",
"pages": "202--229",
"other_ids": {},
"num": null,
"urls": [],
"raw_text": "Rohrer (eds.), Natural Language Parsing and Lin- guistic Theories, Dordrecht, Reidel, 202-229.",
"links": null
}
},
"ref_entries": {
"FIGREF0": {
"uris": null,
"type_str": "figure",
"text": "............. > s\\lP ............. < s",
"num": null
},
"FIGREF1": {
"uris": null,
"type_str": "figure",
"text": "............................. . . . . . . . . . . . . . . . . . . . . . . . .",
"num": null
},
"FIGREF2": {
"uris": null,
"type_str": "figure",
"text": "/NP conj (S\\NP)/VP VP/NP ............... >B (SkWP)Im,",
"num": null
},
"FIGREF3": {
"uris": null,
"type_str": "figure",
"text": "m~)\\C (vP/SP)/mD vPXC~/SP) ............... <T <T CVP/sP) \\ (CVP/sP)/sP) ~\\ (vv/sP) <B vp\\ (VV lSi.) <&> (17) {a, DPa, Px,P~} {]~,DP~,P2, Ps} ::~ {7, DP.y,P1,Pa} (18) a. enjoy :--{{VP, DPvp, Lvp, Rvp}/{NP, L.p, Lnp, R.p}, DPverb, Leerb, R~erb}",
"num": null
},
"TABREF3": {
"html": null,
"content": "<table><tr><td colspan=\"5\">207-210]). They are thereby prevented from captur-</td></tr><tr><td colspan=\"5\">ing a number of generalisations of CCGs, and in fact</td></tr><tr><td colspan=\"2\">exclude functional composition entirely.</td><td/><td/><td/></tr><tr><td>(27) 1</td><td>Gilbert</td><td/><td/><td/><td>2</td><td>walks</td><td>3</td></tr><tr><td/><td colspan=\"5\">{S/{S/{NP, DPg,Lg,Rg},DPg,Lpred, Rpred},Lg,Rg }</td><td>{S/{NP, R~p,L.p,R~p},DP,~,Lw,R~}</td></tr><tr><td>(28) 1</td><td>Gilbert</td><td/><td/><td>2</td><td>walks</td><td>3</td></tr><tr><td/><td colspan=\"4\">{S/{S/{NP, DPg, I,2},DPg,Lpre,~,R~r.d}I,2}</td><td>{S/{NP, R.p,L.p,R,w},DP\",2,3}</td></tr><tr><td>(29) 1</td><td colspan=\"4\">Gilbert {S/{S/{NP, 01)9, 1, 2}, DPg, Lure& R~red}, 1,2} {X/{Y, P2, P2, P3}, P1, P2}</td><td>2</td><td>walks {S/{NP, R~p, L.p, R~p}, DP,~, 2, 3} {Y, P2, P2, P3}</td></tr><tr><td>(3O) 1</td><td colspan=\"2\">Gilbert {S/{S/{NP, 2, 1,2}, 2, 2, 3}, 1, 2}</td><td>2</td><td colspan=\"2\">walks {S/{NP, 2, 1,2}, 2, 2, 3}</td></tr><tr><td/><td colspan=\"2\">{S, 1,3}</td><td/><td/></tr><tr><td>(31) 1</td><td>,Walks {S/{NP, R~p, L.~, R~p}, 1, 2} {Y, P2, P1, P2}</td><td>2</td><td colspan=\"3\">Gilbert {S/ { S/ { N P, 01)9,2, 3}, DP 9, Lpr.d, Rpred}, 2, 3} {X/{Y, P2, Pl, P2}, P2, P3}</td></tr><tr><td colspan=\"6\">(32) .{X, DParg,Larg,Rarg} :=~ {T/{T/{X, DParg,Lar.,Rarg}'DPpred'Lpred'Rp red}'Larg'Rarg}</td></tr></table>",
"type_str": "table",
"num": null,
"text": "pp.(25) {X, DParg,L..rg, R,,rg} => {T/{T/{X, DP,,,'g,L,,rg,R,,,-g},DParg,Lpred,Ra, red},L\"rg, Rar9 }"
}
}
}
} |