Inferensys

Glossary

CoNLL-U Format

The standard tab-separated text format used to represent annotated linguistic data, including token IDs, lemmas, part-of-speech tags, morphological features, and dependency relations, as defined by the Universal Dependencies project.
Data engineer managing feature store on laptop, feature definitions visible, casual data engineering session.
LINGUISTIC DATA INTERCHANGE

What is CoNLL-U Format?

The CoNLL-U format is the standard tab-separated values (TSV) file format defined by the Universal Dependencies project for representing annotated linguistic data, including tokenization, lemmatization, part-of-speech tags, morphological features, and typed dependency relations.

CoNLL-U format is a plain-text, ten-column TSV representation where each line corresponds to a token, and blank lines mark sentence boundaries. The ten fields encode a token's ID, FORM, LEMMA, UPOS, XPOS, FEATS, HEAD, DEPREL, DEPS, and MISC, with underscores used for unspecified values. Comment lines beginning with a hash (#) carry metadata such as sent_id and text.

The format serves as the primary interchange standard for Universal Dependencies (UD) treebanks, enabling interoperability between parsers like the Deep Biaffine Parser and Stanza. Its strict columnar structure allows direct evaluation of Labeled Attachment Score (LAS) and facilitates the representation of both basic and enhanced dependencies through the DEPS column, which captures additional semantic relations beyond surface syntax.

UNIVERSAL DEPENDENCIES STANDARD

Key Features of the CoNLL-U Format

The CoNLL-U format is the tab-separated values (TSV) standard for representing annotated linguistic data in the Universal Dependencies project. It encodes tokenization, morphology, syntax, and semantics in a structured, machine-readable format.

01

10-Column Tabular Structure

Every token occupies a single line with 10 tab-separated fields. Empty lines mark sentence boundaries, and lines starting with # store metadata comments. The rigid column structure ensures consistent parsing across all UD treebanks.

  • ID: Token index (integer) or range for multiword tokens (e.g., 1-2)
  • FORM: The surface form as it appears in the text
  • LEMMA: Base or dictionary form of the word
  • UPOS: Universal part-of-speech tag (e.g., NOUN, VERB)
  • XPOS: Language-specific POS tag (optional, _ if absent)
  • FEATS: Morphological features as Key=Value pairs separated by |
  • HEAD: ID of the syntactic head (0 for root)
  • DEPREL: Universal dependency relation label (e.g., nsubj, obj)
  • DEPS: Enhanced dependency graph as HEAD:REL pairs
  • MISC: Any other annotation as Key=Value pairs
10
Columns per token
02

Multiword Token Representation

The format handles syntactic words that span multiple orthographic tokens (e.g., Spanish 'dámelo' = 'da' + 'me' + 'lo'). A multiword token line uses a range ID (e.g., 1-3) followed by individual token lines with dashed IDs (1-1, 1-2, 1-3). This preserves both the original text segmentation and the syntactic analysis.

  • Range ID line contains the full surface form
  • Sub-token lines carry the morphological and syntactic annotations
  • Enables accurate alignment between raw text and linguistic analysis
03

Morphological Feature Encoding

The FEATS column uses a structured Key=Value notation to encode inflectional and derivational morphology. Multiple features are separated by the pipe character (|), and the underscore (_) indicates no morphological annotation is available.

  • Example: Gender=Fem|Number=Sing|Case=Acc
  • Universal features defined by UD include Animacy, Aspect, Case, Definite, Degree, and 20+ others
  • Enables cross-linguistic queries for specific grammatical phenomena
  • Language-specific extensions can be added as needed
24+
Universal feature categories
04

Enhanced Dependency Graphs

The DEPS column extends basic syntax with additional arcs capturing implicit predicates, shared arguments, and control relationships. Each entry is a HEAD:REL pair, with multiple pairs separated by |. This bridges surface syntax and deeper semantic interpretation.

  • Example: 3:obl:agent|5:nsubj:xsubj
  • Captures null elements and elided material
  • Supports downstream tasks like semantic role labeling and AMR parsing
  • The _ placeholder indicates no enhanced annotation is present
05

Sentence-Level Metadata Comments

Lines beginning with # store structured metadata as key-value pairs. Standard comment keys include sent_id for unique sentence identifiers and text for the raw sentence string. Transliterations, translations, and corpus-specific annotations are also stored here.

  • # sent_id = weblog-blogspot.com_norvig_20060911092800_ENG_20060911_092800-0001
  • # text = What if Google Morphed Into GoogleOS?
  • # translit = ... for scripts requiring romanization
  • Comments precede the token lines they describe
06

Empty Nodes for Ellipsis

The format supports empty syntactic nodes to represent elided or gapped material in coordinated structures. Empty nodes use an ID with a decimal (e.g., 5.1) and carry the _ placeholder in the FORM and LEMMA columns while retaining full morphological and dependency annotations.

  • Example: 'Mary bought a book and John a newspaper' — an empty node represents the elided verb 'bought' in the second clause
  • Enables complete syntactic representation of elliptical constructions
  • Critical for languages with frequent argument dropping
CoNLL-U FORMAT

Frequently Asked Questions

Clear answers to common questions about the CoNLL-U format, the standard tab-separated representation for Universal Dependencies annotation.

The CoNLL-U format is the standard tab-separated values (TSV) file format used by the Universal Dependencies (UD) project to represent annotated linguistic data. It encodes tokenization, lemmatization, part-of-speech tags, morphological features, and dependency syntax in a structured, human-readable plain-text file. Each sentence is represented as a block of lines separated by blank lines, where each token occupies a single line with 10 tab-separated fields. Comment lines begin with a hash (#). The format is designed to be both machine-parseable and manually editable, serving as the primary interchange format for multilingual treebanks and parser training pipelines.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.