Arc-Eager parsing is a deterministic transition-based parsing algorithm that processes a sentence from left to right using a stack and buffer. Unlike the Arc-Standard variant, which delays arc creation until both the head and dependent are fully processed, the Arc-Eager strategy performs a Left-Arc or Right-Arc action immediately when the dependent is on top of the stack and the head is the next token in the buffer. This eager attachment allows the parser to build dependencies incrementally, reducing the stack depth required and enabling the immediate resolution of certain syntactic relations before the head has found its own governor.
Glossary
Arc-Eager Parsing

What is Arc-Eager Parsing?
Arc-Eager parsing is a transition-based dependency parsing strategy that constructs syntactic dependencies as soon as the dependent word is fully processed, enabling left-arc and right-arc actions to be executed eagerly before the head word is complete.
The algorithm defines four core actions: SHIFT (pushing the next buffer token onto the stack), LEFT-ARC (popping the stack top and attaching it as a dependent of the buffer's first token), RIGHT-ARC (attaching the buffer's first token as a dependent of the stack top and pushing it onto the stack), and REDUCE (popping the stack top when it has already found its head). This action set inherently handles projective dependency trees and requires a dynamic oracle during training to define optimal actions from non-gold states, mitigating the error propagation common in greedy, deterministic parsing pipelines.
Key Characteristics of Arc-Eager Parsing
Arc-Eager is a transition-based parsing algorithm that builds dependency arcs as soon as the dependent word is fully processed, enabling left-arc and right-arc actions to be performed eagerly before the head's own dependents are complete.
Eager Attachment Strategy
Unlike Arc-Standard parsing, which delays attachment until the head is complete, Arc-Eager performs Left-Arc and Right-Arc actions immediately when the dependent is on top of the stack. This means a word can receive its head before all of its own dependents are attached, reducing the number of items that must remain on the stack and enabling earlier commitment to syntactic structure.
Four Core Transition Actions
The parser operates with exactly four atomic actions:
- SHIFT: Pushes the next input token from the buffer onto the stack
- LEFT-ARC(l): Attaches the stack top as a dependent of the next buffer token with label l, then pops the stack
- RIGHT-ARC(l): Attaches the next buffer token as a dependent of the stack top with label l, then pushes the buffer token onto the stack
- REDUCE: Pops the stack top, indicating it is fully processed and will receive no more dependents
Preconditions and Constraints
Each action has strict preconditions to ensure valid tree construction:
- LEFT-ARC requires the stack top to not already have a head (no multiple heads)
- RIGHT-ARC can only be applied when the dependent has no head assigned
- REDUCE requires the stack top to already have a head, preventing orphaned tokens
- These constraints guarantee the output is a well-formed, single-root dependency tree without cycles
Linear Time Complexity
Arc-Eager parsing runs in O(n) time for a sentence of length n, as each token is shifted once and reduced at most once. This makes it significantly faster than graph-based alternatives like the Chu-Liu/Edmonds algorithm, which require O(n²) or O(n³) operations. The deterministic, greedy nature eliminates the need for global optimization passes, making it ideal for production NLP pipelines like spaCy.
Projectivity Limitation
The standard Arc-Eager algorithm can only produce projective dependency trees — structures without crossing arcs. This is because the stack-buffer architecture processes words in linear order and cannot create arcs that cross previously established dependencies. For languages with frequent non-projective constructions, such as Czech or Dutch, extensions like swap-based parsing or pseudo-projective transformations are required.
Error Propagation Risk
As a greedy, deterministic algorithm, Arc-Eager makes irreversible decisions at each step. An incorrect attachment early in the sentence cascades into subsequent errors because the parser cannot backtrack. This is mitigated by:
- Dynamic oracles that allow training on non-gold states
- Beam search that maintains multiple hypotheses in parallel
- Deep neural feature extractors that improve individual action prediction accuracy
Arc-Eager vs. Arc-Standard Parsing
A comparison of the two fundamental transition-based dependency parsing algorithms, detailing their operational constraints, action sets, and structural properties.
| Feature | Arc-Eager | Arc-Standard | Hybrid/Swap-Based |
|---|---|---|---|
Parsing Strategy | Eager: Builds arcs as soon as the dependent is fully processed | Delayed: Builds arcs only when the head is complete | Combines eager attachment with swap for non-projectivity |
Arc Creation Timing | Left-Arc and Right-Arc performed immediately | Left-Arc and Right-Arc performed only when head has all dependents | Eager arcs with additional swap transitions |
Projectivity Constraint | Strictly projective only | Strictly projective only | Handles non-projective trees via swap operation |
Stack Item Type | Partially processed heads with unresolved dependents | Fully processed subtrees only | Partially processed heads with swap buffer |
Right-Arc Precondition | Dependent must have no unresolved dependents | Dependent must be a complete subtree | Same as Arc-Eager with swap exceptions |
Left-Arc Precondition | Head must have no left dependents pending | Dependent must be a complete subtree | Same as Arc-Eager with swap exceptions |
Derived Tree Structure | Top-down, left-to-right construction | Bottom-up, head-final construction | Top-down with reordering capability |
Oracle Complexity | Dynamic oracle required for non-deterministic training | Static oracle sufficient for gold-standard derivation | Dynamic oracle with swap cost considerations |
Frequently Asked Questions
Clear, technically precise answers to common questions about the Arc-Eager transition-based dependency parsing strategy, its mechanisms, and its role in syntactic analysis.
Arc-Eager parsing is a transition-based dependency parsing strategy that builds dependency arcs as soon as the dependent word has been fully processed, rather than waiting for the head word to be complete. The algorithm processes a sentence from left to right using a stack, a buffer, and a set of dependency arcs. At each step, it selects one of four actions: SHIFT (move the next buffer token onto the stack), LEFT-ARC (attach the top stack token as a dependent of the next buffer token with a specified relation), RIGHT-ARC (attach the next buffer token as a dependent of the top stack token), or REDUCE (pop the stack). The 'eager' nature means that right-dependents are attached immediately when the dependent is on top of the stack and its head is the first token in the buffer, allowing the parser to build structure incrementally without waiting for the head's own dependents to be resolved. This contrasts with the Arc-Standard strategy, where right-arcs are only created after the head has collected all its dependents.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Core concepts and sibling algorithms that define the transition-based dependency parsing landscape, contrasting eager and lazy attachment strategies.
Arc-Standard Parsing
The canonical lazy transition system where both the head and dependent must be on the stack before an arc is formed. This constraint means right-arc actions can only occur when the dependent has been fully reduced, creating a strict bottom-up derivation.
- Forms dependencies only after the entire subtree of the dependent is complete
- Produces projective trees exclusively
- Simpler state space than Arc-Eager but requires more SHIFT operations
- Often used as the baseline transition system in academic comparisons
Dynamic Oracle Training
A training methodology that defines the set of optimal actions from any valid parser state—even states reached after previous errors. This allows the parser to explore non-gold states during learning and learn recovery strategies.
- Critical for Arc-Eager parsers where early attachment decisions can cascade
- Defines a loss function that measures the cost of each action from the current state
- Enables exploration-based training rather than strict teacher forcing
- Significantly improves robustness to error propagation in greedy decoding
Beam Search Decoding
A non-deterministic search strategy that maintains a fixed number of the most probable partial parse states at each step. Instead of committing to a single greedy action, the parser explores k parallel hypotheses simultaneously.
- Mitigates the error propagation inherent in greedy Arc-Eager parsing
- Beam width of 8–32 typically balances accuracy and speed
- Each state tracks its cumulative log-probability score
- Allows the parser to recover from locally ambiguous attachment decisions by considering global context
Non-Projective Dependency Handling
Arc-Eager parsing naturally produces projective trees, but many languages exhibit crossing arcs due to free word order or long-distance dependencies. Extensions like the Swap transition or pseudo-projective parsing add mechanisms to handle non-projectivity.
- SWAP action: Moves the top stack item back to the buffer to reorder processing
- Pseudo-projective parsing: Converts non-projective training data into projective trees with encoded arc labels, then restores crossings post-hoc
- Languages like Czech, Dutch, and German frequently require non-projective handling
- Adds complexity to the transition system but preserves Arc-Eager's efficiency

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.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us