Thematic roles (also known as theta roles or semantic roles) are generalized categories—such as Agent, Patient, Theme, and Instrument—that describe the function an entity fulfills in the action or state expressed by a predicate. Unlike syntactic relations like 'subject' or 'object,' thematic roles remain constant across different grammatical constructions; the 'breaker' is the Agent whether the sentence is active or passive.
Glossary
Thematic Roles

What are Thematic Roles?
Thematic roles define the underlying semantic relationship a noun phrase has with the main verb of a clause, categorizing participants by the part they play in the event.
These roles form the foundation of the predicate-argument structure and are critical for semantic role labeling (SRL) systems. Lexical resources like VerbNet and FrameNet explicitly map verbs to their permissible thematic role sets, enabling NLP models to generalize understanding beyond surface syntax and perform deep reasoning about 'who did what to whom.'
Core Thematic Roles
Thematic roles (theta roles) are the fundamental semantic categories that define how noun phrases participate in the action or state described by a verb. They abstract away from surface syntax to capture the deep 'who did what to whom' structure of a clause.
Agent
The volitional initiator of an action—the entity that deliberately performs or causes the event.
- Typically animate and capable of intentionality
- Often maps to the grammatical subject in active voice
- Example: 'Mary baked a cake' (Mary is the Agent)
- Contrasts with Force, which is an inanimate causer (e.g., 'The wind shattered the window')
Agents are central to predicate-argument structure and are labeled as ARG0 in PropBank annotation.
Patient
The entity that undergoes the action or experiences a change of state. The Patient is the affected object that exists before and after the event, often altered in some way.
- Prototypically maps to the direct object
- Distinguished from Theme by the change-of-state criterion
- Example: 'The chef broke the egg' (the egg undergoes transformation)
- In FrameNet, Patients appear in frames like Cause_harm or Cause_change_of_position
In PropBank, Patients are typically labeled ARG1 for transitive verbs.
Theme
The entity that moves, is located, or is described—but crucially does not undergo a fundamental change of state. The Theme is the participant whose position or condition is specified.
- Central to verbs of motion, transfer, and location
- Example: 'She placed the book on the shelf' (the book moves but remains unchanged)
- Example: 'The painting is beautiful' (the painting is being described)
- Often conflated with Patient in simplified role inventories
Theme is a core role in VerbNet classifications, particularly for verbs in the put-9.1 and send-11.1 classes.
Instrument
The tool or means by which an Agent accomplishes an action. Instruments are intermediary entities used causally but lack their own volition.
- Typically appears in prepositional phrases with 'with' or 'using'
- Example: 'He cut the rope with a knife'
- Can be promoted to subject position: 'The key opened the door'
- Closely related to the Manner role, which describes how an action is performed
Instruments are annotated as ARGM-MNR or ARG2 in PropBank, depending on the verb's specific frameset.
Beneficiary
The entity for whose benefit an action is performed. The Beneficiary receives advantage or gain from the event without being directly acted upon.
- Often realized as a prepositional phrase with 'for' or an indirect object
- Example: 'She baked a cake for her daughter'
- Example: 'He bought me a gift' (dative construction)
- Distinguished from Recipient, which receives a transferred object
In PropBank, Beneficiaries are typically tagged as ARGM-PRP (purpose) or ARG4 in specific framesets like give-13.1.
Locative
The spatial reference point where an action occurs or where an entity is situated. Locatives ground the event in physical or abstract space.
- Realized through locative prepositions: 'in', 'on', 'at', 'under', 'near'
- Example: 'The meeting happened in the conference room'
- Example: 'She lives in Berlin'
- Subtypes include Source (origin), Goal (destination), and Path (trajectory)
Locatives are annotated as ARGM-LOC in PropBank and are critical for spatial reasoning in semantic parsing tasks like AMR construction.
Frequently Asked Questions
Clear, technical answers to the most common questions about the semantic categories that define the underlying relationships between verbs and their arguments.
Thematic roles (also known as theta roles or semantic roles) are a set of generalized semantic categories that describe the underlying relationship a noun phrase has with the main verb of a clause. They capture the 'who did what to whom' of a sentence by classifying arguments into types such as Agent (the deliberate initiator of an action), Patient (the entity undergoing the action), Theme (the entity that is moved or located), and Instrument (the tool used to perform the action). Unlike syntactic functions like 'subject' or 'object,' thematic roles remain constant across different syntactic realizations. For example, in both 'The engineer deployed the model' and 'The model was deployed by the engineer,' the engineer retains the Agent role and the model retains the Patient role. This abstraction is critical for computational linguistics tasks like Semantic Role Labeling (SRL) , where systems must map surface syntax to deep semantic structures.
Thematic Roles vs. Syntactic Functions
A comparison of generalized semantic categories that describe a noun phrase's relationship to a verb with their corresponding grammatical functions in sentence structure.
| Feature | Thematic Roles | Syntactic Functions | Example |
|---|---|---|---|
Definition | Generalized semantic categories describing the underlying relationship a noun phrase has with the main verb | Grammatical relations a constituent holds within the formal structure of a clause | |
Level of Analysis | Deep semantic structure | Surface grammatical structure | |
Universality | Largely universal across languages | Language-specific and construction-dependent | |
Agent vs. Subject | Entity that volitionally performs an action | Grammatical subject of a clause | The chef (Agent/Subject) baked a cake |
Patient vs. Object | Entity that undergoes the action and changes state | Direct object of a transitive verb | The chef baked a cake (Patient/Object) |
Theme vs. Subject | Entity that moves or is located but does not change state | Subject in passive or unaccusative constructions | The ball (Theme/Subject) rolled down the hill |
Instrument | Entity used to perform an action | Object of a preposition or oblique argument | She cut the rope with a knife (Instrument/Oblique) |
Mapping Consistency | One-to-many mapping to syntactic positions | One-to-many mapping to thematic roles | Agent can be Subject (active) or Oblique (passive) |
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.
Examples in NLP and AI
Thematic roles provide a generalized semantic vocabulary for describing argument structure. The following examples illustrate how these roles manifest in NLP tasks and knowledge representation.
Information Extraction
Thematic roles are the backbone of template filling in information extraction systems. Instead of just identifying entities, systems map them to their functional role in an event.
- Agent: The entity intentionally performing the action
- Patient: The entity undergoing the change of state
- Instrument: The tool or force used to perform the action
Example: In 'Hackers breached the firewall using a zero-day exploit,' an SRL system labels Hackers as Agent, the firewall as Patient, and a zero-day exploit as Instrument.
Question Answering Systems
Modern QA systems use thematic roles to align questions with answer passages by matching role signatures. A 'who' question expects an Agent or Experiencer; a 'what was used' question expects an Instrument.
- Question: 'What did the researcher synthesize the compound with?'
- Role Match: The system searches for an Instrument role linked to the predicate synthesize
- Answer: 'a catalytic converter'
This role-based alignment significantly improves answer accuracy over pure keyword matching.
Machine Translation
Languages encode thematic roles differently through syntax. Agent in an English active sentence may become an oblique object in a Korean passive construction. Neural MT systems implicitly learn these role-to-syntax mappings.
- English: 'John broke the window' (Agent=Subject)
- Japanese: '窓がジョンによって割られた' (Agent=Oblique)
Explicit role labeling during training helps models preserve semantic fidelity across syntactic transformations, reducing errors where the doer and done-to are swapped.
Knowledge Graph Construction
When building enterprise knowledge graphs from unstructured text, thematic roles provide the predicate-argument scaffolding for RDF triple generation.
- Sentence: 'Acme Corp acquired BetaSoft for $2B in Q3'
- Triples Generated:
- (Acme Corp, acquired, BetaSoft) — Agent relation
- (acquisition, has-price, $2B) — Theme attribute
- (acquisition, occurred-in, Q3) — Temporal adjunct
This structured extraction enables deterministic factual grounding for downstream reasoning systems.
Text Summarization
Abstractive summarization models use thematic role awareness to preserve who did what to whom when compressing text. Role salience helps determine which arguments to retain and which to drop.
- Original: 'The committee, after lengthy debate, unanimously approved the controversial zoning amendment.'
- Role Preservation: The Agent (committee) and Patient (zoning amendment) are retained; the manner adjunct is dropped
- Summary: 'The committee approved the zoning amendment.'
This ensures the summary maintains propositional accuracy even when drastically shortened.
Dialogue State Tracking
Conversational AI systems track user intent by filling frame slots that correspond directly to thematic roles. Each turn updates the role assignments dynamically.
- User: 'Book me a flight to London tomorrow morning'
- Slots Filled:
- Theme: flight
- Goal/Destination: London
- Temporal: tomorrow morning
- Missing Role: Source (origin city) — triggers a clarification prompt
This role-based state representation enables robust multi-turn dialogue management.

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