... | @@ -10,6 +10,13 @@ The corpus is released using a variant of the [PARSEME Shared task 2018](http:// |
... | @@ -10,6 +10,13 @@ The corpus is released using a variant of the [PARSEME Shared task 2018](http:// |
|
|
|
|
|
Here we give a minimal description of this format, so that the documentation is self-contained. Please refer to the [cupt format description page](http://multiword.sourceforge.net/cupt-format) for details. Since _cupt_ is based on Conll-U, please also check the Universal Dependencies [Conll-U format description page](http://universaldependencies.org/format.html) and the recommendations for [Conll-U Plus extended format](http://universaldependencies.org/ext-format.html), which we aim to be compatible with. In short, a _cupt_ file contains split sentences, each represented with one token per line, blank lines separating sentences, and comments preceded by hashes (#) to add sentence meta-data such as raw text and sentence IDs. The first line of the _cupt_ file contains special metadata listing the names of each column. Each token on a line contains 11 columns, corresponding to linguistic information about the token's form, morphology and syntax (ID, FORM, LEMMA, UPOS, etc). Tokens roughly correspond to words, except for multiword tokens represented as ranges (see UD's [tokenization guide](http://universaldependencies.org/u/overview/tokenization.html) and PARSEME's page on [words and tokens](http://parsemefr.lif.univ-mrs.fr/parseme-st-guidelines/1.1/?page=wordsandtokens)).
|
|
Here we give a minimal description of this format, so that the documentation is self-contained. Please refer to the [cupt format description page](http://multiword.sourceforge.net/cupt-format) for details. Since _cupt_ is based on Conll-U, please also check the Universal Dependencies [Conll-U format description page](http://universaldependencies.org/format.html) and the recommendations for [Conll-U Plus extended format](http://universaldependencies.org/ext-format.html), which we aim to be compatible with. In short, a _cupt_ file contains split sentences, each represented with one token per line, blank lines separating sentences, and comments preceded by hashes (#) to add sentence meta-data such as raw text and sentence IDs. The first line of the _cupt_ file contains special metadata listing the names of each column. Each token on a line contains 11 columns, corresponding to linguistic information about the token's form, morphology and syntax (ID, FORM, LEMMA, UPOS, etc). Tokens roughly correspond to words, except for multiword tokens represented as ranges (see UD's [tokenization guide](http://universaldependencies.org/u/overview/tokenization.html) and PARSEME's page on [words and tokens](http://parsemefr.lif.univ-mrs.fr/parseme-st-guidelines/1.1/?page=wordsandtokens)).
|
|
|
|
|
|
|
|
### Format of colums 1 to 10: Morpho-syntactic annotation schemes
|
|
|
|
|
|
|
|
The PARSEME-FR annotated corpus comes in two variants for the morpho-syntactic annotations:
|
|
|
|
|
|
|
|
- the original dependency scheme for the [sequoia deep corpus](https://deep-sequoia.inria.fr/)
|
|
|
|
- the [sequoia corpus converted to Universal Dependencies, version 2.3](https://github.com/UniversalDependencies/UD_French-Sequoia/tree/master)
|
|
|
|
|
|
|
|
|
|
### Format of the MWE/NE annotation layer (11th column)
|
|
### Format of the MWE/NE annotation layer (11th column)
|
|
|
|
|
... | @@ -89,12 +96,6 @@ The sentence contains an example of a word (support verb "effectuait") belonging |
... | @@ -89,12 +96,6 @@ The sentence contains an example of a word (support verb "effectuait") belonging |
|
27 . ... *
|
|
27 . ... *
|
|
```
|
|
```
|
|
|
|
|
|
### Morpho-syntactic annotation schemes, and link to the MWE / NE annotations
|
|
### Interaction between syntactic annotation and MWE status
|
|
|
|
|
|
The PARSEME-FR annotated corpus comes in two variants for the morpho-syntactic annotations:
|
|
|
|
|
|
|
|
- the original dependency scheme for the [sequoia deep corpus](https://deep-sequoia.inria.fr/)
|
|
|
|
- the sequoia corpus converted to Universal Dependencies
|
|
|
|
|
|
|
|
**TO BE CONTINUED HERE**
|
|
|
|
|
|
|
|
|
|
** TO BE CONTINUED HERE ** |