You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the english phrase FSTs make strong assumptions about the sentence structure for translation, based on itwewina. This means things like 3s as the standard form in the definition, which is not the case e.g. in WordNet definitions which take the infinitive.
For a search, say, of "I ate", eventually we would have an appropriate analysis to inflect over the definition. In wordnet, we have "take in solid food". Because it's not 3s, the inflection does not change the phrase. If the definition were instead "s/he takes in solid food", then we could inflect it in the results. However, we currently can't (only because of the FST, I've written the code although it needs more testing)
In general the definition structure for the english side should be more flexible, with some way to specify in the system the structure of the definitions or at least accept infinitive-based definitions which seem pretty common in our currently supported target language.
The text was updated successfully, but these errors were encountered:
fbanados
changed the title
English Phrase FST assumes definitions in CW-format
English Phrase FST assumes definitions in itwewina format (not language agnostic)
Jan 11, 2025
Looks like the english phrase FSTs make strong assumptions about the sentence structure for translation, based on itwewina. This means things like 3s as the standard form in the definition, which is not the case e.g. in WordNet definitions which take the infinitive.
For a search, say, of "I ate", eventually we would have an appropriate analysis to inflect over the definition. In wordnet, we have "take in solid food". Because it's not 3s, the inflection does not change the phrase. If the definition were instead "s/he takes in solid food", then we could inflect it in the results. However, we currently can't (only because of the FST, I've written the code although it needs more testing)
In general the definition structure for the english side should be more flexible, with some way to specify in the system the structure of the definitions or at least accept infinitive-based definitions which seem pretty common in our currently supported target language.
The text was updated successfully, but these errors were encountered: