unification based grammar engineering
play

Unification-Based Grammar Engineering Dan Flickinger Stanford - PowerPoint PPT Presentation

Unification-Based Grammar Engineering Dan Flickinger Stanford University & Redbird Advanced Learning danf@stanford.edu Stephan Oepen Oslo University oe@ifi.uio.no ESSLLI 2016; August 1519, 2016 Recognizing the Language of a Grammar


  1. Unification-Based Grammar Engineering Dan Flickinger Stanford University & Redbird Advanced Learning danf@stanford.edu Stephan Oepen Oslo University oe@ifi.uio.no ESSLLI 2016; August 15–19, 2016

  2. Recognizing the Language of a Grammar � C, Σ , P, S � ✬ ✩ S S → NP VP VP → V NP NP VP VP → VP PP NP → NP PP P : kim VP PP PP → P NP V NP NP → kim | sushi | chopsticks P NP V → snores | eats eats sushi with chopsticks P → with ✫ ✪ S All Complete Derivations NP VP • are rooted in the start symbol S ; kim V NP • label internal nodes with cate- gories ∈ C , leafs with words ∈ Σ ; eats NP PP • instantiate a grammar rule ∈ P at P NP sushi each local subtree of depth one. with chopsticks ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (2)

  3. Limitations of Context-Free Grammar Agreement and Valency (For Example) That dog barks. ∗ That dogs barks. ∗ Those dogs barks. The dog chased a cat. ∗ The dog barked a cat. ∗ The dog chased. ∗ The dog chased a cat my neighbors. The cat was chased by a dog. ∗ The cat was chased of a dog. ... ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (3)

  4. Structured Categories in a Unification Grammar • All (constituent) categories in the grammar are typed feature structures; • specific TFS configurations may correspond to ‘traditional’ categories; • labels like ‘S’ or ‘NP’ are mere abbreviations, not elements of the theory.       HEAD noun HEAD verb HEAD verb           �   �     � �      HEAD det    HEAD noun SPR SPR ��     SPR                         COMPS ��   COMPS ��   COMPS ��           phrase word phrase ‘N’ ‘S’ ‘VP’ ‘lexical’ ‘maximal’ ‘intermediate’ ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (4)

  5. Interaction of Lexicon and Phrase Structure Schemata     HEAD 1 HEAD 1       �� SPR           �� − →  , � 2 � SPR 2 SPR             COMPS ��            COMPS 3 COMPS 3 phrase         phrase phrase   ORTH “barks”         HEAD verb  AGR 1 3sg        ORTH “the dog”                       HEAD noun  AGR 3sg        HEAD noun  AGR 1                         �   �    �� SPR  SPR          ��   SPR             COMPS ��             COMPS ��     phrase           COMPS ��     phrase ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (5)

  6. The Type Hierarchy: Fundamentals • Types ‘represent’ groups of entities with similar properties (‘classes’); • types ordered by specificity: subtypes inherit properties of (all) parents; • type hierarchy determines which types are compatible (and which not). *top* *string* *list* feat-struc pos expression *ne-list* *null* phrase noun verb word det root ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (6)

  7. Multiple Inheritance • flyer and swimmer no common descendants: they are incompatible; • flyer and bee stand in hierarchical relationship: they unify to subtype; • flyer and invertebrate have a unique greatest common descendant. *top* animal flyer swimmer invertebrate vertebrate bee fish guppy cod ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (7)

  8. Typed Feature Structure Subsumption • Typed feature structures can be partially ordered by information content; • a more general structure is said to subsume a more specific one;   • *top*  is the most general feature structure (while ⊥ is inconsistent);  • ⊑ (‘square subset or equal’) conventionally used to depict subsumption. Feature structure F subsumes feature structure G ( F ⊑ G ) iff: (1) if path p is defined in F then p is also defined in G and the type of the value of p in F is a supertype or equal to the type of the value of p in G , and (2) all paths that are reentrant in F are also reentrant in G . ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (8)

  9. Feature Structure Subsumption: Examples Signature     FOO x FOO x     TFS 1 : TFS 2 :         BAR x BAR y         a a *top*   FOO y     FOO 1 x   a x     TFS 3 : BAR x TFS 4 :         BAR 1         BAZ x a     b b y Feature structure F subsumes feature structure G ( F ⊑ G ) iff: (1) if path p is defined in F then p is also defined in G and the type of the value of p in F is a supertype or equal to the type of the value of p in G , and (2) all paths that are reentrant in F are also reentrant in G . ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (9)

  10. Typed Feature Structure Unification • Decide whether two typed feature structures are mutually compatible; • determine combination of two TFSs to give the most general feature structure which retains all information which they individually contain; • if there is no such feature structure, unification fails (depicted as ⊥ ); • unification monotonically combines information from both ‘input’ TFSs; • relation to subsumption the unification of two structures F and G is the most general TFS which is subsumed by both F and G (if it exists). • ⊓ (‘square set intersection’) conventionally used to depict unification. ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (10)

  11. Typed Feature Structure Unification: Examples Signature     FOO x FOO x     TFS 1 : TFS 2 :         BAR x BAR y         a a *top*   FOO y     FOO 1 x   a x     TFS 3 : BAR x TFS 4 :         BAR 1         BAZ x a     b b y   FOO 1 y       TFS 1 ⊓ TFS 2 ≡ TFS 2 TFS 1 ⊓ TFS 3 ≡ TFS 3 TFS 3 ⊓ TFS 4 ≡ BAR 1         BAZ x     b ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (11)

  12. Notational Conventions • lists not available as built-in data type; abbreviatory notation in TDL: < a, b > ≡ [ FIRST a, REST [ FIRST b, REST *null* ] ] • underspecified (variable-length) list: < a ... > ≡ [ FIRST a, REST *list* ] • difference (open-ended) lists; allow concatenation by unification: <! a !> ≡ [ LIST [ FIRST a, REST #tail ], LAST #tail ] • built-in and ‘non-linguistic’ types pre- and suffixed by asterisk ( *top* ); • strings (e.g. “chased” ) need no declaration; always subtypes of *string* ; • strings cannot have subtypes and are (thus) mutually incompatible. ABabcdfghiejkl esslli —  -aug-  Grammar Engineering (12)

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend