conll#
type: Ontology
comment: CoNLL-RDF ontology Column structure for various one-word-per-line TSV formats as used, e.g., by CorpusWorkBench/SketchEngine and for most CoNLL Shared Tasks. The input format is “vertical” or “word-per-line (WPL)” text, as defined at the University of Stuttgart in the 1990s. Words are written one word per line, so each line contains one word, number or punctuation mark. (https://www.sketchengine.eu/documentation/preparing-corpus-text/) history 2021-10-09 added CoNLL-09 as alias for CoNLL-X (CC) 2020-05-26 added encodings, reserved characters and CoNLL-99 (CC) 2020-01-08 added lexical formats (CC) 2019-09-07 added CWB and SketchEngine formats (CC) 2019-09-04 :dialect recast as ObjectProperty (CC) 2019-08-30 created (CC) contributors CC - Christian Chiarcos, chiarcos@informatik.uni-frankfurt.de
description: Ontology covering the following CoNLL TSV dialects and related one-word-per-line formats. In chronological order, these are: - CWB (Corpus WorkBench) format (1994) [column structure only]: http://txm.sourceforge.net/doc/cwb/technical-manual.pdf - TreeTagger format (1994) [column structure only]: https://www.ims.uni-stuttgart.de/forschung/ressourcen/werkzeuge/treetagger.en.html - SketchEngine format [column structure only]: https://www.sketchengine.eu/documentation/preparing-corpus-text/ - CoNLL-99 format: https://www.clips.uantwerpen.be/conll99/npb/, data under ftp://ftp.cis.upenn.edu/pub/chunker/ - CoNLL-00 format: https://www.clips.uantwerpen.be/conll2000/chunking/ - CoNLL-01 format: https://www.clips.uantwerpen.be/conll2001/clauses/ - CoNLL-02 format: https://www.clips.uantwerpen.be/conll2002/ner/ - CoNLL-03 format: https://www.clips.uantwerpen.be/conll2003/ner/ - CoNLL-04 format: https://www.cs.upc.edu/~srlconll/st04/conll04st-release.tar.gz (conll04st-release/README) - CoNLL-05 format: https://www.cs.upc.edu/~srlconll/conll05st-release/README - CoNLL-06 format: https://ilk.uvt.nl/conll/ (link broken, no information available, probably identical to CoNLL-07 format) - CoNLL-07 format: https://depparse.uvt.nl/DataFormat.html - CoNLL-08 format: http://surdeanu.info/conll08/conll08.pdf - CoNLL-09/CoNLL-X format: http://ufal.mff.cuni.cz/conll2009-st/task-description.html - CoNLL-11 format: http://conll.cemantix.org/2011/data.html - CoNLL-12 format: http://conll.cemantix.org/2012/data.html - UniMorph format: (CoNLL–SIGMORPHON 2017/2018 shared tasks, https://sigmorphon.github.io/sharedtasks/2017/) http://unimorph.github.io/ - CoNLL-U formats: (used in CoNLL 2017/2018 shared tasks on Multilingual Parsing from Raw Text to Universal Dependencies) http://universaldependencies.org/ CoNLL-U: https://universaldependencies.org/format.html (v.1: https://universaldependencies.org/docsv1/format.html) CoNLL-U Plus: https://universaldependencies.org/ext-format.html - PropBank CoNLL…
version info: TODO: check whether not to migrate Word and Sentence into conll namespace. Note that this breaks downward-compability.

format dialect
comment: A CoNLL dialect is a one-word-per-line TSV format with a specific configuration of columns. Note that selected TSV dialects may contain additional markup in SGML (Corpus WorkBench), XML (SketchEngine) or comments (CoNLL-U Plus) which are not covered by this ontology. A dialect representation requires at least one name (rdfs:label) and at least one pointer to documentation or sample data (rdfs:isDefinedBy). It can contain several column mappings, but as some formats support user-defined columns, this is optional. Also, a dialect may use non-standard symbols for separating blocks (sentences, normally " "), rows (words, normally " "), columns (annotations, normally " "), for marking comments (normally "#") or for representing the absence of an annotation (normally "_"). Again, this is optional. If no reserved symbols are declared, the defaults are assumed.
subclass of: Restriction
  on property: label
  min cardinality: 1
subclass of: Restriction
  on property: isDefinedBy
  min cardinality: 1
subclass of: Restriction
  on property: blockSeparator
  max cardinality: 1
subclass of: Restriction
  on property: colSeparator
  max cardinality: 1
subclass of: Restriction
  on property: rowSeparator
  max cardinality: 1
subclass of: Restriction
  on property: emptyAnnotationMarker
  max cardinality: 1
subclass of: Restriction
  on property: commentMarker
  max cardinality: 1

hasMapping
type: AnnotationProperty
domain: Property
comment: Assigns a CoNLL property a ColumnMapping. Note that this cannot be formally axiomatized in OWL.
range: ColumnMapping

property
type: ObjectProperty
version info: Inverse of :hasMapping, provided for OWL reasoning, do not use for data modelling
inverse of: hasMapping

column
type: DatatypeProperty
comment: column number (starting with 1) in a particular CoNLL or TSV format
domain: ColumnMapping
range: int

dialect
type: ObjectProperty
comment: format identifier, identifies the CoNLL dialect
domain: ColumnMapping
range: format dialect

ColumnMapping
subclass of: Restriction
  on property: dialect
  min cardinality: 1
subclass of: Restriction
  on property: dialect
  max cardinality: 1
subclass of: Restriction
  on property: column
  cardinality: 1
comment: n-ary annotation property that maps a CoNLL-RDF property to a column (integer value starting with 1) in a particular CoNLL or TSV dialect (identified as a string). Optionally, the encoding strategy can be indicated. If these are not, we assume headEncoding for HEAD, columnEncoding for *ARGS (see :argument), and plainEncoding for everything else.

CoNLL encoding
type: Class
comment: Different CoNLL/TSV formats use different strategies to represent annotations, e.g., those that span multiple words. The subclasses of this concept represent frequently applied techniques. The 'default' encoding strategy is :plainEncoding, i.e., string labels attached to individual words, not surrounded by special characters such as double quotes.

encoding
type: ObjectProperty
comment: Mark the encoding style of a particular column. Can be used for converting between different representations. By default, we assume headEncoding for HEAD, columnEncoding for *ARGS (see :argument), and plainEncoding for everything else. These three should thus be left implicit.
domain: ColumnMapping
range: CoNLL encoding

hasReservedSymbol
type: DatatypeProperty
comment: For a given format, characters or substrings may serve a special function, e.g., as comment marker or column separator. Subproperties of this property should implement those symbols. If no explicit value is provided, we assume that a default holds as defined for individual properties. Do not use this property directly.
range: string
domain: format dialect

blockSeparator
type: DatatypeProperty
sub property of: hasReservedSymbol
comment: A block separator indicates breaks between sequences of rows that should be loaded into a single RDF graph by CoNLLStreamExtractor, e.g., a sentence. The default is "\\n\\n" (NEWLINE NEWLINE).

rowSeparator
type: DatatypeProperty
sub property of: hasReservedSymbol
comment: A row separator indicates breaks between rows, i.e., normally a word with its annotations. The default is "\\n" (NEWLINE).

colSeparator
type: DatatypeProperty
sub property of: hasReservedSymbol
comment: A column separator indicates breaks between columns, i.e., normally between different annotations of the same word. The default is "\\t" (TAB).

commentMarker
type: DatatypeProperty
sub property of: hasReservedSymbol
comment: A comment marker marks the beginning of a comment. We assume that the comment extends until the end of the line. The default is "#" (HASH).

emptyAnnotationMarker
type: DatatypeProperty
sub property of: hasReservedSymbol
comment: In classical CoNLL formats, the absence of an annotation is marked by "_" (in some variants also "-"), in IOBES and related encodings, the absence of an annotation is marked by "O". Note that it is technically possible to specify this to be an empty string. The default is "_" (UNDERSCORE).

nextSentence
type: FunctionalProperty
type: ObjectProperty
comment: NIF: This property can be used to make resources of nif:Sentence and nif:Word traversable, it can not be assumed that no gaps or whitespaces between sentences or words exist, i.e. string adjacency is not mandatory. In CoNLL-RDF, neither inverse nor transitive versions of this property are employed. Otherwise, the use of nif:nextSentence is compliant with the original NIF definition, and thus, we do not introduce a novel vocabulary element for this purpose.
range: Sentence
domain: Sentence

nextWord
type: FunctionalProperty
type: ObjectProperty
comment: In CoNLL-RDF, the nif:nextWord property is used to link adjacent words (adjacent rows with text and/or annotation). Note that we do not use the transitive or inverse versions provided by NIF. Also note that nif:nextWord should *not* hold between words that belong to different sentences. Our use of nif:nextWord is more restricted than in NIF, but it is compliant with it, so that we do not introduce an novel vocabulary element.
range: Word
domain: Word

sentence
type: ObjectProperty
deprecated: true
comment: NIF definition: This property links words and other structures to their sentence. In CoNLL-RDF, this function is taken over by conll:HEAD, hence, this property is deprecated. This property is preserved in the CoNLL-RDF ontology in order to explicate this difference from NIF.
range: Sentence

Sentence
type: Class
comment: NIF definition: A sentence. In CoNLL-RDF, a nif:Sentence corresponds to a block of rows that contain text and/or annotations and that are separated from other sentences by an empty line.

Word
type: Class
comment: NIF definition: The Word class represents strings that are tokens or words. A string is a Word, if it is a word. We don't nitpic about whether it is a a pronoun, a name, a punctuation mark or an apostrophe or whether it is separated by white space from another Word or something else. ... In CoNLL-RDF, a nif:Word corresponds to a row in a CoNLL TSV file that contains text and/or annotations. Normally, this will be a (linguistic) word, but as NIF delegates the definitions of nif:Word to external tokenizers, we delegate the definition of nif:Word to data providers. If rows are being used for morpheme-level segmentation instead of word segmentation, they will still be considered as nif:Word.

Corpus Workbench format
type: format dialect
label: CWB format
comment: Only the first column is fixed, all other columns can be configured. Cover column structure only, no SGML markup.

TreeTagger format
type: format dialect
comment: cover column structure only, no SGML markup.

SketchEngine format
type: format dialect
label: NoSketchEngine format
comment: SketchEngine performs POS tagging and lemmatization, up to the first three columns are thus fixed. Cover column structure only, no XML markup.

CoNLL-99 format
type: format dialect
comment: For a more detailed explanation of the format see Ramshaw and Marcus (1995), also cf. https://www.aclweb.org/anthology/E99-1023.pdf ("IOB1" format)

CoNLL-00 format
type: format dialect

CoNLL-01 format
type: format dialect

CoNLL-02 format
type: format dialect

CoNLL-03 format
type: format dialect

CoNLL-04 format
type: format dialect
comment: See https://www.cs.upc.edu/~srlconll/st04/conll04st-release.tar.gz, conll04st-release/README)

CoNLL-05 format
type: format dialect

CoNLL-06 format
type: format dialect
comment: Source link provided under https://www.conll.org/previous-tasks is broken, no information available, probably identical to CoNLL-07 format

CoNLL-07 format
type: format dialect

CoNLL-08 format
type: format dialect

CoNLL-X format
type: format dialect

CoNLL-09 format
type: format dialect

CoNLL-11 format
type: format dialect

CoNLL-12 format
type: format dialect

CoNLL-U
type: format dialect
comment: Used in CoNLL 2017/2018 shared tasks on Multilingual Parsing from Raw Text to Universal Dependencies, cf. http://universaldependencies.org/

CoNLL-U Plus
type: format dialect

PropBank CoNLL format
type: format dialect
label: PropBank Skel format

UniversalPropositions CoNLL format
type: format dialect
label: UniversalPropositions Skel format

Open Multilingual WordNet tab format
type: format dialect
comment: If we set the block separator to " " and row separator to "", this means that every line is processed individually. This is useful for transformations and thus default within CoNLL-RDF. If this is not specified, the entire file/stream is processed as a single RDF graph.

UniMorph format
type: format dialect
comment: Used in CoNLL–SIGMORPHON 2017/2018 shared tasks, https://sigmorphon.github.io/sharedtasks/2017/
comment: If we set the block separator to " " and row separator to "", this means that every line is processed individually. This is useful for transformations and thus default within CoNLL-RDF. If this is not specified, the entire file/stream is processed as a single RDF graph.

Translation Inference Across Dictionaries TSV format
type: format dialect
label: TIAD-2017 TSV format
label: TIAD-2019 TSV format
label: TIAD-2020 TSV format
comment: If we set the block separator to " " and row separator to "", this means that every line is processed individually. This is useful for transformations and thus default within CoNLL-RDF. If this is not specified, the entire file/stream is processed as a single RDF graph.

plain encoding
type: CoNLL encoding
comment: A word (form) is assigned a string label without internal structure, e.g., for POS annotation: house/NN

IOBES encoding
type: CoNLL encoding
comment: For an annotation that covers a span of tokens, e.g., in named entity annotation, the string label is prefixed with a marker for the position of the word in the span, i.e. B- (begin of span), I- (middle of span), E- (end of span), S- (single token, begin and end of span) or O (no annotation). Note that this is not to be used for recursive structures, see BracketEncoding, instead. Example: Peter/B-PERSON Jackson/E-PERSON is/O ...

IOB encoding
type: CoNLL encoding
comment: Simplified IOBES encoding, using B- (begin of a single-token or multi-token sequence), I- (middle or end of a multi-token sequence), O (no annotation). From O and B-, we can infer that a preceding B- corresponds to an IOBES S- and that a preceding I- corresponds to an IOBES E- annotation. Note that this is not to be used for recursive structures, see BracketEncoding, instead. Example: Peter/B-PERSON Jackson/I-PERSON is/O ...

bracket encoding
type: CoNLL encoding
comment: Encoding of recursive spans, e.g., for phrase structure syntax, based on conventions of the Penn Treebank. Begin of phrase is marked with an opening bracket, end of phrase with a closing bracket. The opening bracket is followed by an optional phrase label. The content word is replaced by *. Example: Penn annotation: (S (NP (NN Peter) (NN Jackson)) (VP (VB is) ...)) one-word per line encoding: Peter (S (NP (NN *) Jackson (NN *)) is (VP (VB *) ... * )) This is well-suited for encoding continuous phrases.

column encoding
type: CoNLL encoding
comment: This is a convention for encoding semantic role annotations: in a reference columns, say, PRED, all predicates are marked. For each predicate in the sentence, then, a column is added that contains the arguments. Note that this is added for presentational reasons and the sake of completeness only. For the actual modelling, see the :arguments property.

head encoding
type: CoNLL encoding
comment: In dependency syntax, the HEAD column contains a numerical reference to a word (by token offset within the sentence or ID). Note that this is added for presentational reasons and the sake of completeness only. For the actual modelling, see the :HEAD property.

DatatypeProperty
type: FunctionalProperty
comment: Abstract data type property for text and annotations in CoNLL TSV files. This property must be instantiated before being used. In CoNLL-RDF, the domain must be a nif:Word, range must be a string, and its subproperties must be functional.
domain: Word
range: string

ObjectProperty
comment: Abstract property for relations, e.g., syntactic relations (HEAD column) or semantic roles (argument columns following the predicate column). All CoNLL properties point from one word (row) to something else (sentence or other word).
domain: Word

DOCUMENT_ID
sub property of: DatatypeProperty
label: FILE_NAME
comment: Document ID This is a variation on the document filename (http://conll.cemantix.org/2011/data.html)
version info: roughly equivalent to the filename column in the PropBank skel format (cf. https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md)
has mapping: ColumnMapping
  column: 1
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
  dialect: PropBank CoNLL format

PART_NUMBER
sub property of: DatatypeProperty
comment: Part number Some files are divided into multiple parts numbered as 000, 001, 002, ... etc. (http://conll.cemantix.org/2011/data.html)
has mapping: ColumnMapping
  column: 2
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format

SENTENCE_ID
sub property of: DatatypeProperty
comment: sentence ID (https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md)
has mapping: ColumnMapping
  column: 2
  dialect: PropBank CoNLL format

ID
sub property of: DatatypeProperty
label: WORD_NUMBER
label: TOKEN_INDEX
comment: ID - Token counter, starting at 1 for each new sentence. (https://depparse.uvt.nl/DataFormat.html) ID: Word index, integer starting at 1 for each new sentence; may be a range for tokens with multiple words. (https://universaldependencies.org/docsv1/format.html) token index (https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md)
version info: For annotations of single sentences, this column is systematically named ID. In CoNLL-11, it has been named "word number".
has mapping: ColumnMapping
  column: 1
  dialect: CoNLL-07 format
  dialect: CoNLL-08 format
  dialect: CoNLL-X format
  dialect: CoNLL-U
  dialect: UniversalPropositions CoNLL format
has mapping: ColumnMapping
  column: 3
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
  dialect: PropBank CoNLL format

FORM
sub property of: DatatypeProperty
label: WRITTEN_REP
comment: Word form or punctuation symbol. (https://depparse.uvt.nl/DataFormat.html) Until CoNLL-05 and in CoNLL-11, the label for this column was WORD. CoNLL-07 introduced FORM as an alternative label (and generalization?). The CoNLL-RDF ontology supports both versions, but using the original terminology (WORD) is encouraged for linguistic annotations (not for lexical formats). In lexicon formats, FORM can be used for the (written representation of) a the lexical form of a lexical entry (ontolex:writtenRep, ontolex:Form), e.g., in TIAD-TSV. Note that ontolex:canonicalForm would be reserved for the LEMMA. For the sake of consistency, lexical formats should use FORM, note WORD. Also note that TIAD-TSV written representations are Turtle strings, i.e., they may be enclosed by double quotes and complemented with language tags. This feature is not being used for TIAD-2017, TIAD-2019, or TIAD-2020 data, but for the TIAD-TSV format of the ACoLi Dictionary Collection (https://github.com/acoli-repo/acoli-dicts)
has mapping: ColumnMapping
  column: 1
  dialect: Translation Inference Across Dictionaries TSV format
has mapping: ColumnMapping
  column: 2
  dialect: CoNLL-07 format
  dialect: CoNLL-08 format
  dialect: CoNLL-X format
  dialect: CoNLL-U
  dialect: UniversalPropositions CoNLL format
has mapping: ColumnMapping
  column: 3
  dialect: UniMorph format

WORD
sub property of: FORM
comment: Word form in an annotated text (not in a lexical resource, cf. FORM), typically string-identical with the annotated data (unlike normalized forms such as LEMMA). The first item on each line is a word (https://www.clips.uantwerpen.be/conll2003/ner/)
has mapping: ColumnMapping
  column: 1
  dialect: TreeTagger format
  dialect: Corpus Workbench format
  dialect: SketchEngine format
  dialect: CoNLL-99 format
  dialect: CoNLL-00 format
  dialect: CoNLL-01 format
  dialect: CoNLL-02 format
  dialect: CoNLL-03 format
  dialect: CoNLL-04 format
  dialect: CoNLL-05 format
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
  dialect: PropBank CoNLL format

LEXICAL_ENTRY
sub property of: ObjectProperty
comment: OntoLex lexical entry URI as provided by TIAD-TSV, must be a URI. Original TIAD abbreviation was lex_entry_a.
has mapping: ColumnMapping
  column: 2
  dialect: Translation Inference Across Dictionaries TSV format

LEXICAL_SENSE
sub property of: ObjectProperty
comment: OntoLex lexical sense (word sense) as provided by TIAD-TSV, must be a URI. Note that this must not be confused with WORD_SENSE, which is a string identifier.
has mapping: ColumnMapping
  column: 3
  dialect: Translation Inference Across Dictionaries TSV format

TRANSLATION_URI
sub property of: ObjectProperty
comment: OntoLex translation object, as provided by TIAD-TSV, must be a URI. Note that this must not be confused with TRANSLATION, which is a string.
has mapping: ColumnMapping
  column: 4
  dialect: Translation Inference Across Dictionaries TSV format

TRANSLATION_SENSE_URI
sub property of: LEXICAL_SENSE
comment: OntoLex sense URI of a translation (description language/target language expression). TIAD-TSV label is sense_b.
label: SENSE_B
has mapping: ColumnMapping
  column: 5
  dialect: Translation Inference Across Dictionaries TSV format

TRANSLATION_ENTRY
sub property of: LEXICAL_ENTRY
comment: OntoLex lexical entry URI of the translation. TIAD-TSV label is lex_entry_b. Revised here for readability.
has mapping: ColumnMapping
  column: 6
  dialect: Translation Inference Across Dictionaries TSV format

TRANSLATION
sub property of: FORM
comment: Written representation of the translation in TIAD-TSV. TIAD label is written_rep_b. Not to be confused with TRANSLATION_URI, which is a URI. This is a plain string with optional language typing (cf. FORM).
label: WRITTEN_REP_B
has mapping: ColumnMapping
  column: 7
  dialect: Translation Inference Across Dictionaries TSV format

LEMMA
sub property of: DatatypeProperty
label: ROOT
comment: Lemma information (in linguistic annotation), canonical form of a lexical entry (in machine-readable dictionaries) lemma information (https://www.ims.uni-stuttgart.de/forschung/ressourcen/werkzeuge/treetagger.en.html) Lemma or stem (depending on particular data set) of word form, or an underscore if not available. (https://depparse.uvt.nl/DataFormat.html)
version info: Corresponds to ROOT in the (original) CWB format: "Root for the base form of that word" (https://arxiv.org/pdf/cmp-lg/9408005.pdf). Otherwise systematically labelled LEMMA.
has mapping: ColumnMapping
  column: 3
  dialect: TreeTagger format
  dialect: SketchEngine format
  dialect: CoNLL-07 format
  dialect: CoNLL-08 format
  dialect: CoNLL-X format
  dialect: CoNLL-U
  dialect: OWM
has mapping: ColumnMapping
  column: 1
  dialect: UniMorph format

PLEMMA
sub property of: LEMMA
comment: The P-columns (PLEMMA, PPOS, PFEAT, PHEAD and PDEPREL) are the autoamtically predicted variants of the gold-standard LEMMA, POS, FEAT, HEAD and DEPREL columns. (http://ufal.mff.cuni.cz/conll2009-st/task-description.html)
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-X format

POS
sub property of: DatatypeProperty
label: POSTAG
label: TAG
comment: [T]he second [item on each line is] a part-of-speech (POS) tag (https://www.clips.uantwerpen.be/conll2003/ner/) POSTAG: Fine-grained part-of-speech tag, where the tagset depends on the language, or identical to the coarse-grained part-of-speech tag if not available. (https://depparse.uvt.nl/DataFormat.html)
version info: The abbreviation POSTAG was only used in CoNLL-07. CoNLL-08 provides two POS columns, one for gold annotation (GPOS), one for automated annotation (PPOS), we assume that GPOS and POS are identical. CoNLL-X uses POS, again. The SketchEngine documentation uses both POS and TAG. TIAD-TSV uses LexInfo URIs for POS annotation. If these are to be treated as :ObjectProperties, use POS_URI. In most cases, it will be sufficient/preferrable to treat them as as plain strings. Then, use POS as column label.
has mapping: ColumnMapping
  column: 2
  dialect: TreeTagger format
  dialect: Corpus Workbench format
  dialect: SketchEngine format
  dialect: CoNLL-99 format
  dialect: CoNLL-00 format
  dialect: CoNLL-01 format
  dialect: CoNLL-03 format
  dialect: CoNLL-04 format
has mapping: ColumnMapping
  column: 3
  dialect: CoNLL-05 format
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-08 format
has mapping: ColumnMapping
  column: 5
  dialect: CoNLL-07 format
  dialect: CoNLL-X format
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
  dialect: PropBank CoNLL format
has mapping: ColumnMapping
  column: 8
  dialect: Translation Inference Across Dictionaries TSV format

POS_URI
sub property of: ObjectProperty
comment: POS column in TIAD-TSV, must resolve to a URI, hence not to be confused with POS (with is a string).
has mapping: ColumnMapping
  column: 8
  dialect: Translation Inference Across Dictionaries TSV format

UPOSTAG
sub property of: POS
comment: UPOSTAG: Universal part-of-speech tag drawn from our revised version of the Google universal POS tags. (https://universaldependencies.org/docsv1/format.html)
version info: UD naming simplified in analogy with POS(TAG). Note that UniversalPropositions label this as POS, but emphasize that this is a UD POS, i.e., UPOS (https://github.com/System-T/UniversalPropositions)
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-U
has mapping: ColumnMapping
  column: 3
  dialect: UniversalPropositions CoNLL format

XPOSTAG
sub property of: POS
comment: XPOSTAG: Language-specific part-of-speech tag; underscore if not available. (https://universaldependencies.org/docsv1/format.html)
version info: naming simplified in analogy with POS(TAG)
has mapping: ColumnMapping
  column: 5
  dialect: CoNLL-U

CPOSTAG
sub property of: POS
comment: CPOSTAG: Coarse-grained part-of-speech tag, where tagset depends on the language. (https://depparse.uvt.nl/DataFormat.html)
version info: CoNLL-07 used the abbreviation CPOSTAG, simplified in analogy with POS(TAG)
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-07 format

PPOS
sub property of: POS
comment: PPOS: Predicted POS tag. (http://surdeanu.info/conll08/conll08.pdf)
has mapping: ColumnMapping
  column: 5
  dialect: CoNLL-08 format
has mapping: ColumnMapping
  column: 6
  dialect: CoNLL-X format

SPLIT_FORM
sub property of: FORM
comment: Tokens split at hyphens and slashes. (http://surdeanu.info/conll08/conll08.pdf)
has mapping: ColumnMapping
  column: 6
  dialect: CoNLL-08 format

SPLIT_LEMMA
sub property of: LEMMA
comment: Predicted lemma of SPLIT_FORM. (http://surdeanu.info/conll08/conll08.pdf)
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-08 format

PPOSS
sub property of: POS
comment: Predicted POS tags of the split forms. (http://surdeanu.info/conll08/conll08.pdf)
has mapping: ColumnMapping
  column: 8
  dialect: CoNLL-08 format

FEATS
sub property of: DatatypeProperty
label: FEAT
comment: Unordered set of syntactic and/or morphological features (depending on the particular language), separated by a vertical bar (|), or an underscore if not available. (https://depparse.uvt.nl/DataFormat.html)
version info: CoNLL-07 used the column label FEATS, CoNLL-X used FEAT
has mapping: ColumnMapping
  column: 6
  dialect: CoNLL-07 format
  dialect: CoNLL-U
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-X format
has mapping: ColumnMapping
  column: 3
  dialect: UniMorph format

PFEAT
sub property of: FEATS
comment: The P-columns (PLEMMA, PPOS, PFEAT, PHEAD and PDEPREL) are the autoamtically predicted variants of the gold-standard LEMMA, POS, FEAT, HEAD and DEPREL columns. (http://ufal.mff.cuni.cz/conll2009-st/task-description.html)
has mapping: ColumnMapping
  column: 8
  dialect: CoNLL-X format

CHUNK
sub property of: DatatypeProperty
comment: Text chunking consists of dividing a text in syntactically correlated parts of words. For example, the sentence He reckons the current account deficit will narrow to only # 1.8 billion in September . can be divided as follows: [NP He ] [VP reckons ] [NP the current account deficit ] [VP will narrow ] [PP to ] [NP only # 1.8 billion ] [PP in ] [NP September ] . ... The chunk tags contain the name of the chunk type, for example I-NP for noun phrase words and I-VP for verb phrase words. (https://www.clips.uantwerpen.be/conll2000/chunking/)
has mapping: ColumnMapping
  column: 3
  encoding: IOB encoding
  dialect: CoNLL-00 format
  dialect: CoNLL-01 format
  dialect: CoNLL-03 format
  dialect: CoNLL-04 format
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-05 format
  encoding: bracket encoding

CHUNK
sub property of: CHUNK
label: NOMINAL CHUNK
comment: Annotation of nominal chunks, with verbal chunks excluded, e.g., [NP He ] reckons [NP the current account deficit ] will narrow to [NP only # 1.8 billion ] [PP in ] [NP September ] .
has mapping: ColumnMapping
  column: 3
  encoding: IOB encoding
  dialect: CoNLL-99 format

CHUNK
sub property of: CHUNK
label: NOMINAL CHUNK
comment: Note that CoNLL-99 has two levels of NCHUNK annotation, apparently by different annotators.
has mapping: ColumnMapping
  column: 4
  encoding: IOB encoding
  dialect: CoNLL-99 format

CHUNK
sub property of: CHUNK
label: VERBAL CHUNK
comment: Annotation of verbal chunks, with nominal chunks excluded, e.g., He [VP reckons ] the current account deficit [VP will narrow ] to only # 1.8 billion PP in NP September .
has mapping: ColumnMapping
  column: 5
  encoding: IOB encoding
  dialect: CoNLL-99 format

CLAUSE
sub property of: DatatypeProperty
comment: Clauses are word sequences which contain a subject and a predicate. (https://www.clips.uantwerpen.be/conll2001/clauses/) In the CoNLL-01 format (shared task part 3), a bracket notation based on the Penn Treebank syntax was used, using S as its only label.
has mapping: ColumnMapping
  column: 4
  encoding: IOB encoding
  dialect: CoNLL-01 format
  dialect: CoNLL-99 format
  dialect: CoNLL-04 format
has mapping: ColumnMapping
  column: 5
  encoding: bracket encoding
  dialect: CoNLL-05 format

FULL_SYNT
sub property of: DatatypeProperty
label: PARSE_BIT
comment: Parse bit: This is the bracketed structure broken before the first open parenthesis in the parse, and the word/part-of-speech leaf replaced with a *. The full parse can be created by substituting the asterix with the "([pos] [word])" string (or leaf) and concatenating the items in the rows of that column. (http://conll.cemantix.org/2011/data.html) Introduced in CoNLL-05 as FULL_SYNT, but we follow CoNLL-11/PropBank for readability.
has mapping: ColumnMapping
  column: 6
  encoding: bracket encoding
  dialect: CoNLL-05 format
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
has mapping: ColumnMapping
  column: 5
  dialect: PropBank CoNLL format

WORD_SENSE
sub property of: DatatypeProperty
comment: Word sense This is the word sense of the word in Column 3. (http://conll.cemantix.org/2011/data.html)
has mapping: ColumnMapping
  column: 9
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format

LEXICAL_CONCEPT
sub property of: DatatypeProperty
comment: OWM: "Princeton WordNet" (synset ID), terminology here follows OntoLex-Lemon and WordNet conventions
label: SYNSET
has mapping: ColumnMapping
  column: 1
  dialect: Open Multilingual WordNet tab format

PROPERTY
sub property of: DatatypeProperty
comment: relation identifier, in OMW, this contains the static string "lemma" or (for French) "fra:lemma". Terminology here follows RDF terminology.
label: RELATION
has mapping: ColumnMapping
  column: 2
  dialect: Open Multilingual WordNet tab format

SPEAKER
sub property of: DatatypeProperty
label: AUTHOR
comment: Speaker/Author This is the speaker or author name where available. Mostly in Broadcast Conversation and Web Log data. (http://conll.cemantix.org/2011/data.html)
has mapping: ColumnMapping
  column: 10
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format

NER
sub property of: DatatypeProperty
label: NE
comment: Named entities are phrases that contain the names of persons, organizations, locations, times and quantities. Example: [PER Wolff ] , currently a journalist in [LOC Argentina ] , played with [PER Del Bosque ] in the final years of the seventies in [ORG Real Madrid ] . (https://www.clips.uantwerpen.be/conll2002/ner/)
version info: CoNLL-02 and CoNLL-03 referred to this data as NER annotations, CoNLL-05 as NE annotations
has mapping: ColumnMapping
  column: 2
  dialect: CoNLL-02 format
  dialect: CoNLL-05 format
has mapping: ColumnMapping
  column: 4
  dialect: CoNLL-03 format
has mapping: ColumnMapping
  column: 11
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
has mapping: ColumnMapping
  column: 5
  dialect: CoNLL-04 format

HEAD
sub property of: ObjectProperty
label: HEAD_ID
comment: Head of the current token, which is either a value of ID or zero ('0'). Note that depending on the original treebank annotation, there may be multiple tokens with an ID of zero. (https://depparse.uvt.nl/DataFormat.html)
version info: In CoNLL-RDF, the sentence URI is formed with the virtual word number 0. This corresponds to the way how CoNLL identifies syntactic roots. In CoNLL-RDF, the HEAD property (cast as an object property/foreign key) thus takes over the function of nif:sentence. In UniversalPropositions renamed as HeadId (https://github.com/System-T/UniversalPropositions)
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-07 format
  dialect: CoNLL-U
has mapping: ColumnMapping
  column: 9
  dialect: CoNLL-08 format
  dialect: CoNLL-X format
has mapping: ColumnMapping
  column: 4
  dialect: UniversalPropositions CoNLL format

HEAD2
sub property of: HEAD
label: PHEAD
label: SECEDGE
comment: Second head annotation. Note that the *kind* of dependency annotation in relation to HEAD is undetermined and has been used differently in different CoNLL Shared Tasks. CoNLL-07: PHEAD (projective head): Projective head of current token, which is either a value of ID or zero ('0'), or an underscore if not available. Note that depending on the original treebank annotation, there may be multiple tokens an with ID of zero. The dependency structure resulting from the PHEAD column is guaranteed to be projective (but is not available for all languages), whereas the structures resulting from the HEAD column will be non-projective for some sentences of some languages (but is always available). CoNLL-X: PHEAD (predicted head): The P-columns (PLEMMA, PPOS, PFEAT, PHEAD and PDEPREL) are the autoamtically predicted variants of the gold-standard LEMMA, POS, FEAT, HEAD and DEPREL columns. (http://ufal.mff.cuni.cz/conll2009-st/task-description.html)
version info: In CoNLL-RDF, the label PHEAD is used. We follow the naming pattern introduced in the TIGER XML format ("secondary edge", https://www.ims.uni-stuttgart.de/forschung/ressourcen/werkzeuge/TIGERSearch/doc/html/TigerXML.html). However, the TIGER XML format has been extended for semantic role annotations with yet another layer of edges (SALSA), so that CoNLL-RDF employs a numbering scheme instead of adjectival prefixes for naming. For SALSA, cf. Erk, K., & Pado, S. (2004). A Powerful and Versatile XML Format for Representing Role-semantic Annotation. In Proc. LREC 2004.
has mapping: ColumnMapping
  column: 9
  dialect: CoNLL-07 format
has mapping: ColumnMapping
  column: 10
  dialect: CoNLL-X format

EDGE
sub property of: DatatypeProperty
label: DEPREL
comment: Dependency relation to the HEAD. The set of dependency relations depends on the particular language. Note that depending on the original treebank annotation, the dependency relation may be meaningful or simply 'ROOT'. (https://depparse.uvt.nl/DataFormat.html)
version info: CoNLL-RDF recommends using the label EDGE as introduced in the TIGER XML format (https://www.ims.uni-stuttgart.de/forschung/ressourcen/werkzeuge/TIGERSearch/doc/html/TigerXML.html). In CoNLL-07 and UniversalPropositions, this column is labelled DEPREL, resp. Deprel.
has mapping: ColumnMapping
  column: 8
  dialect: CoNLL-07 format
  dialect: CoNLL-U
has mapping: ColumnMapping
  column: 10
  dialect: CoNLL-08 format
has mapping: ColumnMapping
  column: 5
  dialect: UniversalPropositions CoNLL format
has mapping: ColumnMapping
  column: 11
  dialect: CoNLL-X format

EDGE2
sub property of: EDGE
label: PDEPREL
comment: Dependency relation to the PHEAD [HEAD2 -- CC], or an underscore if not available. The set of dependency relations depends on the particular language. Note that depending on the original treebank annotation, the dependency relation may be meaningful or simply 'ROOT'. (https://depparse.uvt.nl/DataFormat.html)
version info: Naming pattern follows HEAD2 and EDGE. In CoNLL-07 and CoNLL-X, this column was labelled PDEPREL (but with different definitions).
has mapping: ColumnMapping
  column: 10
  dialect: CoNLL-07 format
has mapping: ColumnMapping
  column: 12
  dialect: CoNLL-X format

DEPS
sub property of: DatatypeProperty
comment: List of secondary dependencies (head-deprel pairs). (https://universaldependencies.org/docsv1/format.html)
version info: This was introduced as an alternative way to express secondary edges.
has mapping: ColumnMapping
  column: 9
  dialect: CoNLL-U

MISC
sub property of: DatatypeProperty
comment: Any other annotation. (https://universaldependencies.org/docsv1/format.html)
has mapping: ColumnMapping
  column: 10
  dialect: CoNLL-U

PRED
sub property of: DatatypeProperty
label: ROLESET
label: FRAME
comment: PRED Rolesets of the semantic predicates in this sentence. (http://surdeanu.info/conll08/conll08.pdf) The roleset column gives the actual sense used, and that sense provides roleset specific meanings for each of the numbered arguments. (https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md) Note that this concatenates information alternatively provided in columns TARGETS/PRED_LEMMA (lemma of predicate) and VS/PRED_FRAMESET (sense number), these are thus superseded by PRED and should no longer be used.
version info: Named "Frame" in UniversalPropositions (https://github.com/System-T/UniversalPropositions)
has mapping: ColumnMapping
  column: 11
  dialect: CoNLL-08 format
has mapping: ColumnMapping
  column: 7
  dialect: PropBank CoNLL format
has mapping: ColumnMapping
  column: 6
  dialect: UniversalPropositions CoNLL format
has mapping: ColumnMapping
  column: 14
  dialect: CoNLL-X format

FILLPRED
sub property of: DatatypeProperty
comment: FILLPRED contains Y for lines where PRED is/should be filled. (http://ufal.mff.cuni.cz/conll2009-st/task-description.html)
has mapping: ColumnMapping
  column: 13
  dialect: CoNLL-X format

VS
sub property of: DatatypeProperty
label: Predicate Frameset ID
comment: VS: VerbNet sense of target verbs [in Semantic Role Labelling -- CC]. These are hand-crafted annotations that will be available only in training and development sets (not for the test set). (https://www.cs.upc.edu/~srlconll/conll05st-release/README) Predicate Frameset ID This is the PropBank frameset ID of the predicate in Column 7. (http://conll.cemantix.org/2011/data.html)
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-05 format
has mapping: ColumnMapping
  column: 8
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format

TARGETS
sub property of: DatatypeProperty
label: PREDICATE_LEMMA
label: FRAME_FILE
comment: Target verbs [of Semantic Role Labelling -- CC], marking N predicative verbs. This column (...) specifies the governing verbs of the propositions to be analyzed. Each target verb is in its infinitive form. (https://www.cs.upc.edu/~srlconll/st04/conll04st-release.tar.gz: README) The "frame file" column lets you know which ".xml" file contains the actual semantic form for the predicate in question (which is not always the same as the predicate: one must reference "lighten.xml" for lighten_up.02). (https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md) Predicate lemma The predicate lemma is mentioned for the rows for which we have semantic role information. All other rows are marked with a "-" (http://conll.cemantix.org/2011/data.html) In the CoNLL-04 format, this column was followed by a variable number of argument columns. These are treated differently than other conll columns in that the annotations become property labels if alphanumerical labels are provided (as with CoNLL-05). The CoNLL-04 bracketing notation is not directly supported by CoNLL-RDF, but can be easily produced out of the bracket notation.
has mapping: ColumnMapping
  column: 6
  dialect: CoNLL-04 format
  dialect: PropBank CoNLL format
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
has mapping: ColumnMapping
  column: 8
  dialect: CoNLL-05 format

ARG
sub property of: ObjectProperty
sub property of: ColumnEncoding
label: PROP
label: APREDs
label: PRED_ARGs
label: ROLE
comment: Columns with argument labels for each semantic predicate following textual order. (http://surdeanu.info/conll08/conll08.pdf) Every column after the eighth is a predicate, in order that they appear in the sentence. Thus the ninth column is for the "have" auxiliary as token #1, the tenth is for "like.02" which is token #8, and so forth. (https://github.com/propbank/propbank-release/blob/master/docs/conll-conversion-notes.md) Abstract property for arguments in semantic role annotations. Here, each argument role label (bereft of IOBES- and C-/R-prefixes) is represented as an independent object property. In the CoNLL-04 Shared Task on Semantic Role Labelling, the TARGET column was followed by "[f]or each of the N target verbs, a column in Start-End format specifying the arguments of the proposition." (https://www.cs.upc.edu/~srlconll/st04/conll04st-release.tar.gz: README) The roles in CoNLL-04 etc were defined by PropBank, with the following role inventory in the test set: predicate: V; core roles: A0, A1, A2, A3, A4, A5; modifiers: AM-ADV, AM-CAU, AM-DIR, AM-DIS, AM-EXT, AM-LOC, AM-MNR, AM-MOD, AM-NEG, AM-PNC, AM-PRD, AM-TMP PropBank (https://github.com/propbank/propbank-release) uses roughly the same role inventory, but with expanded abbreviations: ARG0, ARG1, etc. We follow CoNLL-04 practice, but provide PropBank labels as label information. predicate: V; core roles: ARG0, ARG1, ARG1-DSP, ARG2, ARG2-DSP, ARG3, ARG3-DSP, ARG4, ARG5, ARGA; modifiers: ARGM-ADJ, ARGM-ADV, ARGM-CAU, ARGM-COM, ARGM-CXN, ARGM-DIR, ARGM-DIS, ARGM-EXT, ARGM-GOL, ARGM-LOC, ARGM-LVB, ARGM-MNR, ARGM-MOD, ARGM-NEG, ARGM-PRD, ARGM-PRP, ARGM-PRR, ARGM-REC, ARGM-TMP Note that the mapping described below refers to the first column only.
version info: CoNLL-04 introduced these columns as "argument" and we follow this practice, in CoNLL-05, they were referred to as "PROPS", in CoNLL-08 as "ARG", in CoNLL-X as "APREDs", in CoNLL-11/12 as "predicate arguments", in UniversalPropositions as "role". PropBank does not provide an explicit name for this data. CoNLL-RDF parses groups of columns as argument columns only with reference to another column. If this column is called PRED (cf. :PRED), the CoNLL-RDF label would be PRED_ARGs.
has mapping: ColumnMapping
  column: 7
  dialect: CoNLL-04 format
  dialect: UniversalPropositions CoNLL format
has mapping: ColumnMapping
  column: 12
  dialect: CoNLL-08 format
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format
has mapping: ColumnMapping
  column: 15
  dialect: CoNLL-X format
has mapping: ColumnMapping
  column: 9
  dialect: CoNLL-05 format
has mapping: ColumnMapping
  column: 8
  dialect: PropBank CoNLL format

V
sub property of: ARG

A0
sub property of: ARG
label: ARG0

A1
sub property of: ARG
label: ARG1

A2
sub property of: ARG
label: ARG2

A3
sub property of: ARG
label: ARG3

A4
sub property of: ARG
label: ARG4

A5
sub property of: ARG
label: ARG5

AA
sub property of: ARG
label: ARGA

A1-DSP
sub property of: ARG
label: ARG1-DSP

A2-DSP
sub property of: ARG
label: ARG2-DSP

A3-DSP
sub property of: ARG
label: ARG3-DSP

A4-DSP
sub property of: ARG
label: ARG4-DSP

A5-DSP
sub property of: ARG
label: ARG5-DSP

AM-ADJ
sub property of: ARG
label: ARGM-ADJ

AM-ADV
sub property of: ARG
label: ARGM-ADV

AM-CAU
sub property of: ARG
label: ARGM-CAU

AM-COM
sub property of: ARG
label: ARGM-COM

AM-CXN
sub property of: ARG
label: ARGM-CXN

AM-DIR
sub property of: ARG
label: ARGM-DIR

AM-DIS
sub property of: ARG
label: ARGM-DIS

AM-EXT
sub property of: ARG
label: ARGM-EXT

AM-GOL
sub property of: ARG
label: ARGM-GOL

AM-LOC
sub property of: ARG
label: ARGM-LOC

AM-LVB
sub property of: ARG
label: ARGM-LVB

AM-MNR
sub property of: ARG
label: ARGM-MNR

AM-MOD
sub property of: ARG
label: ARGM-MOD

AM-NEG
sub property of: ARG
label: ARGM-NEG

AM-PNC
sub property of: ARG
label: ARGM-PNC

AM-PRD
sub property of: ARG
label: ARGM-PRD

AM-PRP
sub property of: ARG
label: ARGM-PRP

AM-PRR
sub property of: ARG
label: ARGM-PRR

AM-REC
sub property of: ARG
label: ARGM-REC

AM-TMP
sub property of: ARG
label: ARGM-TMP

COREFERENCE
sub property of: DatatypeProperty
comment: Coreference Coreference chain information encoded in a parenthesis structure. (http://surdeanu.info/conll08/conll08.pdf)
version info: The position is after PRED_ARGs, hence 13 is only the first possible column.
has mapping: ColumnMapping
  column: 13
  dialect: CoNLL-11 format
  dialect: CoNLL-12 format