Difference between revisions of "Ideas for Google Summer of Code/Integration and debugging tools for Grammatical Framework"
Jump to navigation
Jump to search
(→Tools) |
|||
Line 4: | Line 4: | ||
* Morphological analyser |
* Morphological analyser |
||
** Input: Text stream, PGF grammar file |
|||
** Output: Tokenised and morphologically analysed text |
|||
* Disambiguator |
* Disambiguator |
||
** Input: Morphologically analysed text, PGF grammar file |
|||
** Output: The analysed text without the analyses not found in the parse trees below a certain probability threshold (n-best). e.g. 1-best would have only the morphological analyses which are found in the 1-best parse tree. |
|||
* Lexicon expander |
* Lexicon expander |
||
** Input: |
|||
** Output: Full form list with surface forms and lexical forms |
|||
==Coding challenge== |
==Coding challenge== |
Revision as of 17:34, 11 February 2015
The objective of this task is to create a suite of tools for Grammatical Framework to facilitate interoperability with Apertium and other tools.
Tools
- Morphological analyser
- Input: Text stream, PGF grammar file
- Output: Tokenised and morphologically analysed text
- Disambiguator
- Input: Morphologically analysed text, PGF grammar file
- Output: The analysed text without the analyses not found in the parse trees below a certain probability threshold (n-best). e.g. 1-best would have only the morphological analyses which are found in the 1-best parse tree.
- Lexicon expander
- Input:
- Output: Full form list with surface forms and lexical forms
Coding challenge
- Install Grammatical Framework
- Install Apertium
- Write a program using Haskell or C to retrieve the morphological analysis of a word from the PGF library and print it out in Apertium format.