Dependency Syntax and Universal Dependencies › Summary

Michael BrenndoerferMay 5, 20252 min read
Language AI HandbookAll chapters
Part 7 of 67Linguistic Form: Morphology and Syntax
Chapter 47Dependency Syntax and Universal Dependencies › Summary
Reading section 12 of 13 · Summary · 2 minSection 12 of 13 · 2 min

Section 12 of 13 · 2 min read

Dependency Syntax and Universal Dependencies › SummarySection view · Sections in this chapter12 / 13 ↓
Reading tools Definitions, links & notes

Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.

Article links

Make inline references clickable

Notes & comments

Dependency syntax represents grammatical relations as directed, labelled arcs between syntactic words. In the basic UD representation every word has one incoming arc when artificial node 0 is included, exactly one word has HEAD=0, and the graph is connected and acyclic. A valid graph is not automatically a correct linguistic analysis.

UD normally connects content words directly and attaches related function words to them. Bound morphology remains a property of a word, whereas a separate case-marking word can appear as a dependency node. Shared inventories increase cross-linguistic parallelism without erasing language-specific syntax or annotation conventions.

Projectivity connects dependency structure to linear word order: every word between a head and dependent must be dominated by that head. In our relative-clause example, yesterday violates that condition for the arc from dog to Terrier. The other intervening words belong to dog's subtree. Including the artificial root arc matters when using a crossing-arcs drawing as the test.

CoNLL-U separates word forms, lemmas, POS tags, morphology, basic heads and labels, enhanced dependencies, and miscellaneous annotations. Its integer words, multiword-token ranges, and decimal empty-node identifiers serve different purposes. The bounded reader in this chapter preserves ten fields for basic integer-ID records and explicitly rejects the other record types.

The executable examples read three hand-written sentence analyses, validate their basic-tree constraints, draw two of the trees, and detect projectivity violations. They inspect annotations rather than predict them. The next chapter turns to algorithms that infer structures. The following chapter examines structured prediction and parsing evaluation.

Comments

Add to the conversation

A question, a correction, or an example from your own work.

No comments yet. Be the first to share your thoughts!

Newsletter

Stay up to date

Get new articles, book updates, and notes on AI and technology.

Unsubscribe at any time. Privacy policy