Difference between revisions of "Talk:Automatically trimming a monodix"
Jump to navigation
Jump to search
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | == HFST: possible to overcome compound overgeneration? == |
||
| − | ==Alternate implementation methods== |
||
| − | Trimming while reading the XML file might have lower memory usage (who knows, untested), but seems like more work, since pardefs are read and turned into FST's before we get to an "initial" state and then attached at the end of regular entries. |
||
| + | Assuming we ''don't use flags'', we can compile an HFST transducer through [[ATT]] format to a working lttoolbox transducer. |
||
| − | [[Image:Product-automaton-intersection.png|thumb|400px|right|product automaton for intersection]] |
||
| − | The '''product automaton''' for intersection, marks as final only state-pairs where both parts of the state-pair are final in the original automata. Minimisation removes unreachable state-pairs. However, this quickly blows up in memory usage since it creates ''all'' possible state pairs first (cartesian product), not just the useful ones. |
||
| + | Now the issue is that compounds are plain transitions back into some lexicon, without the compound-only-L/compound-R tags, so even though lt-trim should trim the compounds correctly (by treating them like <j/> transitions), the resulting analyser will over-generate: |
||
| − | https://github.com/unhammer/lttoolbox/branches has some experiments, see e.g. branches product-intersection and df-intersection (the latter is the currently used implementation) |
||
| + | <pre>jīvitarēkha/jīvitarēkha<n><sg><nom>/jīvitaṁ<n><cmp>+rēkha<n><sg><nom></pre> |
||
| − | <br clear="all" /> |
||
| + | Ie. we will get non-lexicalised compound analyses along with the lexicalised ones. |
||
| − | == Compounds vs trimming in HFST == |
||
| + | One way to overcome this is to first compile the analyser from the ATT, then: |
||
| − | The sme.lexc can't be trimmed using the simple HFST trick, due to compounds. |
||
| + | * go through it building a new version, but on seeing a +, we: |
||
| + | ** replace the transition with a single compound-only-L tag transitioning into final state |
||
| + | ** let partial=copy_until_final(the_plus_transition) and make a transition from start into partial, and we connect the final state of partial with a single tag compound-R into the final state of our new FST |
||
| + | If the function copy_until_final sees a +, that transition is discarded, but a compound-only-L tag is added. |
||
| − | Say you have '''cake n sg''', '''cake n pl''', '''beer n pl''' and '''beer n sg''' in monodix, while bidix has '''beer n''' and '''wine n'''. The HFST method without compounding is to intersect '''(cake|beer) n (sg|pl)''' with '''(beer|wine) n .*''' to get '''beer n (sg|pl)'''. |
||
| − | But HFST represents compounding as a transition from the end of the singular noun to the beginning of the (noun) transducer, so a compounding HFST actually looks like |
||
| − | : '''((cake|beer) n sg)*(cake|beer) n (sg|pl)''' |
||
| − | The intersection of this with |
||
| − | : '''(beer|wine) n .*''' |
||
| − | is |
||
| − | : '''(beer n sg)*(cake|beer) n (sg|pl) | beer n pl''' |
||
| − | when it should have been |
||
| − | : '''(beer n sg)*(beer n (sg|pl)''' |
||
| + | Note: this compounding method won't let you do stuff like "only allow adj adj or noun noun compounds" like you can in HFST. |
||
| + | ::You can do that in the morphotactics though (e.g. adjective paradigms only redirect to the adjectivestem lexicon.) - [[User:Francis Tyers|Francis Tyers]] ([[User talk:Francis Tyers|talk]]) 13:33, 22 May 2014 (CEST) |
||
| − | Lttoolbox doesn't represent compounding by extra circular transitions, but instead by a special restart symbol interpreted while analysing. |
||
| + | |||
| − | lt-trim is able to understand compounds by simply skipping the compund tags |
||
| + | : Uh, what happens if you simply specify compound-R and compound-only-L tags in the lexc? |
||
| + | |||
| + | ::This is also an option, while we were at it I'd choose a prettier couple of symbols though ;) - [[User:Francis Tyers|Francis Tyers]] ([[User talk:Francis Tyers|talk]]) 13:33, 22 May 2014 (CEST) |
||
| + | |||
| + | |||
| + | Say we have the FST "bidix", can we create "<code>bidix [^+]* (+ bidix [^+]*)*</code>" (where + is just the literal join symbol) and trim with that? |
||
| + | : seems to work! |
||
Latest revision as of 14:47, 20 June 2014
HFST: possible to overcome compound overgeneration?[edit]
Assuming we don't use flags, we can compile an HFST transducer through ATT format to a working lttoolbox transducer.
Now the issue is that compounds are plain transitions back into some lexicon, without the compound-only-L/compound-R tags, so even though lt-trim should trim the compounds correctly (by treating them like <j/> transitions), the resulting analyser will over-generate:
jīvitarēkha/jīvitarēkha<n><sg><nom>/jīvitaṁ<n><cmp>+rēkha<n><sg><nom>
Ie. we will get non-lexicalised compound analyses along with the lexicalised ones.
One way to overcome this is to first compile the analyser from the ATT, then:
- go through it building a new version, but on seeing a +, we:
- replace the transition with a single compound-only-L tag transitioning into final state
- let partial=copy_until_final(the_plus_transition) and make a transition from start into partial, and we connect the final state of partial with a single tag compound-R into the final state of our new FST
If the function copy_until_final sees a +, that transition is discarded, but a compound-only-L tag is added.
Note: this compounding method won't let you do stuff like "only allow adj adj or noun noun compounds" like you can in HFST.
- You can do that in the morphotactics though (e.g. adjective paradigms only redirect to the adjectivestem lexicon.) - Francis Tyers (talk) 13:33, 22 May 2014 (CEST)
- Uh, what happens if you simply specify compound-R and compound-only-L tags in the lexc?
- This is also an option, while we were at it I'd choose a prettier couple of symbols though ;) - Francis Tyers (talk) 13:33, 22 May 2014 (CEST)
Say we have the FST "bidix", can we create "bidix [^+]* (+ bidix [^+]*)*" (where + is just the literal join symbol) and trim with that?
- seems to work!
