The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
Error code: DatasetGenerationError
Exception: CastError
Message: Couldn't cast
@context: struct<@language: string, @vocab: string, arrayShape: string, citeAs: string, column: string, confor (... 673 chars omitted)
child 0, @language: string
child 1, @vocab: string
child 2, arrayShape: string
child 3, citeAs: string
child 4, column: string
child 5, conformsTo: string
child 6, containedIn: string
child 7, cr: string
child 8, data: struct<@id: string, @type: string>
child 0, @id: string
child 1, @type: string
child 9, dataBiases: string
child 10, dataCollection: string
child 11, dataType: struct<@id: string, @type: string>
child 0, @id: string
child 1, @type: string
child 12, dct: string
child 13, extract: string
child 14, field: string
child 15, fileProperty: string
child 16, fileObject: string
child 17, fileSet: string
child 18, format: string
child 19, includes: string
child 20, isArray: string
child 21, isLiveDataset: string
child 22, jsonPath: string
child 23, key: string
child 24, md5: string
child 25, parentField: string
child 26, path: string
child 27, personalSensitiveInformation: string
child 28, recordSet: string
child 29, references: string
child 30, regex: string
child 31, repeated: string
child 32, replace: string
child 33, sc: string
child 34, separator: string
child 35, source: string
child 36, subField: string
child 37, transform: string
child 38, rai: string
child 39, prov: string
@type: string
distribution: list<item: struct<@type: str
...
1 chars omitted)
child 0, @type: string
child 1, prov:type: struct<@id: string>
child 0, @id: string
child 2, prov:label: string
child 3, sc:description: string
child 4, prov:wasAttributedTo: list<item: struct<@type: string, @id: string, prov:label: string, sc:description: string>>
child 0, item: struct<@type: string, @id: string, prov:label: string, sc:description: string>
child 0, @type: string
child 1, @id: string
child 2, prov:label: string
child 3, sc:description: string
datePublished: timestamp[s]
version: string
inLanguage: string
isAccessibleForFree: bool
citeAs: string
beliefs: list<item: struct<actor: string, belief: string, labels: struct<order: string, truth_status: string, (... 114 chars omitted)
child 0, item: struct<actor: string, belief: string, labels: struct<order: string, truth_status: string, knowledge_ (... 102 chars omitted)
child 0, actor: string
child 1, belief: string
child 2, labels: struct<order: string, truth_status: string, knowledge_access: string, representation: string, conten (... 55 chars omitted)
child 0, order: string
child 1, truth_status: string
child 2, knowledge_access: string
child 3, representation: string
child 4, content_type: string
child 5, mental_source: string
child 6, context: string
story_id: int64
story: string
story_category: string
to
{'story_id': Value('int64'), 'story_category': Value('string'), 'story': Value('string'), 'beliefs': List({'actor': Value('string'), 'belief': Value('string'), 'labels': {'order': Value('string'), 'truth_status': Value('string'), 'knowledge_access': Value('string'), 'representation': Value('string'), 'content_type': Value('string'), 'mental_source': Value('string'), 'context': Value('string')}})}
because column names don't match
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1827, in _prepare_split_single
for key, table in generator:
^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 613, in wrapped
for item in generator(*args, **kwargs):
~~~~~~~~~^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 343, in _generate_tables
self._cast_table(pa_table, json_field_paths=json_field_paths),
~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/json/json.py", line 132, in _cast_table
pa_table = table_cast(pa_table, self.info.features.arrow_schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
return cast_table_to_schema(table, schema)
File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
raise CastError(
...<3 lines>...
)
datasets.table.CastError: Couldn't cast
@context: struct<@language: string, @vocab: string, arrayShape: string, citeAs: string, column: string, confor (... 673 chars omitted)
child 0, @language: string
child 1, @vocab: string
child 2, arrayShape: string
child 3, citeAs: string
child 4, column: string
child 5, conformsTo: string
child 6, containedIn: string
child 7, cr: string
child 8, data: struct<@id: string, @type: string>
child 0, @id: string
child 1, @type: string
child 9, dataBiases: string
child 10, dataCollection: string
child 11, dataType: struct<@id: string, @type: string>
child 0, @id: string
child 1, @type: string
child 12, dct: string
child 13, extract: string
child 14, field: string
child 15, fileProperty: string
child 16, fileObject: string
child 17, fileSet: string
child 18, format: string
child 19, includes: string
child 20, isArray: string
child 21, isLiveDataset: string
child 22, jsonPath: string
child 23, key: string
child 24, md5: string
child 25, parentField: string
child 26, path: string
child 27, personalSensitiveInformation: string
child 28, recordSet: string
child 29, references: string
child 30, regex: string
child 31, repeated: string
child 32, replace: string
child 33, sc: string
child 34, separator: string
child 35, source: string
child 36, subField: string
child 37, transform: string
child 38, rai: string
child 39, prov: string
@type: string
distribution: list<item: struct<@type: str
...
1 chars omitted)
child 0, @type: string
child 1, prov:type: struct<@id: string>
child 0, @id: string
child 2, prov:label: string
child 3, sc:description: string
child 4, prov:wasAttributedTo: list<item: struct<@type: string, @id: string, prov:label: string, sc:description: string>>
child 0, item: struct<@type: string, @id: string, prov:label: string, sc:description: string>
child 0, @type: string
child 1, @id: string
child 2, prov:label: string
child 3, sc:description: string
datePublished: timestamp[s]
version: string
inLanguage: string
isAccessibleForFree: bool
citeAs: string
beliefs: list<item: struct<actor: string, belief: string, labels: struct<order: string, truth_status: string, (... 114 chars omitted)
child 0, item: struct<actor: string, belief: string, labels: struct<order: string, truth_status: string, knowledge_ (... 102 chars omitted)
child 0, actor: string
child 1, belief: string
child 2, labels: struct<order: string, truth_status: string, knowledge_access: string, representation: string, conten (... 55 chars omitted)
child 0, order: string
child 1, truth_status: string
child 2, knowledge_access: string
child 3, representation: string
child 4, content_type: string
child 5, mental_source: string
child 6, context: string
story_id: int64
story: string
story_category: string
to
{'story_id': Value('int64'), 'story_category': Value('string'), 'story': Value('string'), 'beliefs': List({'actor': Value('string'), 'belief': Value('string'), 'labels': {'order': Value('string'), 'truth_status': Value('string'), 'knowledge_access': Value('string'), 'representation': Value('string'), 'content_type': Value('string'), 'mental_source': Value('string'), 'context': Value('string')}})}
because column names don't match
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1369, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
~~~~~~~~~~~~~~~~~~~~~~~~~^
builder, max_dataset_size_bytes=max_dataset_size_bytes
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
)
^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 948, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1694, in _prepare_split
for job_id, done, content in self._prepare_split_single(
~~~~~~~~~~~~~~~~~~~~~~~~~~^
gen_kwargs=gen_kwargs, job_id=job_id, **_prepare_split_args
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
):
^
File "/usr/local/lib/python3.14/site-packages/datasets/builder.py", line 1880, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
story_id int64 | story_category string | story string | beliefs list |
|---|---|---|---|
1 | Ambiguous Story Task | Xiao Hong and Xiao Fang watch other children play on the playground. They chat about some interesting things happening on the playground and discuss going to the park together after school. Suddenly, Xiao Hong gives Xiao Fang a look and looks in the direction of the swing. Then, Xiao Hong smiles at Xiao Fang. Xiao Fang... | [
{
"actor": "world",
"belief": "Xiao Hong and Xiao Fang watch other children play on the playground",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Action/Event",
"mental_source": "Narrati... |
2 | Ambiguous Story Task | Jianning and Mingkai are the co-captains of the football team. They still lack one team member. They joke that the remaining unselected players are "the best players". After a while, Mingkai does not speak, winks at Jianning, and then looks at Taotao, Taotao is one of the remaining unselected players. Mingkai turns his... | [
{
"actor": "world",
"belief": "Jianning and Mingkai are the co-captains of the football team",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narratio... |
3 | Ambiguous Story Task | Dehua and Sanming are company employees, they are competing for a promotion opportunity. Today is Sanming's birthday, he enjoys a small birthday cake alone. Lingling is the company supervisor, she is having a private conversation with Dehua in the pantry. Sanming sees from a distance that Lingling quietly gives Dehua a... | [
{
"actor": "world",
"belief": "Dehua and Sanming are company employees",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",
"context": "... |
4 | Ambiguous Story Task | Xiao Li and Xiao Wang rest by the swimming pool in the resort. They see Ah Zhen and Ah Hong reading on the loungers not far away, then they exchange a look. Xiao Wang nudges Xiao Li with his elbow, silently mouthing "pretty girls". Xiao Li gives a wink back, they laugh and look at each other, then carefully walk toward... | [
{
"actor": "world",
"belief": "Xiao Li and Xiao Wang rest by the swimming pool in the resort",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Action/Event",
"mental_source": "Narration",
... |
5 | Ambiguous Story Task | Xiao Ming and Xiao Yun are classmates, they prepare a group project. Today, the teacher lets each group share their progress. Xiao Ming is very confident in his ideas, he prepares to share at the meeting. Before the discussion starts, Xiao Yun tells Xiao Ming that she can help him share to avoid his nervousness, Xiao M... | [
{
"actor": "world",
"belief": "Xiao Ming and Xiao Yun are classmates",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",
"context": "Ne... |
6 | Ambiguous Story Task | Li Ming and Zhang Hua are assigned to an important project, their performance in this project affects promotion. The day before the project is about to end, Li Ming temporarily leaves the office, Zhang Hua then walks to Li Ming's computer and quickly hits a few keys. Zhang Hua sees Xiao Chen looking at him, smiles at h... | [
{
"actor": "world",
"belief": "Li Ming and Zhang Hua are assigned to an important project",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",... |
7 | Ambiguous Story Task | In the office, Wang Qiang is the project team leader, and Zhang Wei is Wang Qiang's old deputy. The project team recently brings in a new member Li Li, Wang Qiang and Zhang Wei do not know much about her technical background. Today, Wang Qiang and Zhang Wei arrange for Li Li to complete a task independently, and this t... | [
{
"actor": "world",
"belief": "Wang Qiang is the project team leader",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",
"context": "Ne... |
8 | Ambiguous Story Task | One afternoon, the tense atmosphere in the company seems thicker than usual. Xuemei observes Junbo handling a very picky customer. She pretends to focus on her own work, but in fact, she constantly pays attention to the interaction between Junbo and the customer. Junbo tries to maintain a professional attitude, but he ... | [
{
"actor": "world",
"belief": "The tense atmosphere in the company seems thicker than usual",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Contents/Physical State",
"mental_source": "Nar... |
9 | Ambiguous Story Task | Wang Qiang, Li Ming, and Zhao Min all work in the same company. Recently, there is a division of opinions within the office due to a new policy. Li Ming and Zhao Min are the representatives of these two factions, while Wang Qiang is a regular staff member. One day, the company holds an informal gathering, Wang Qiang he... | [
{
"actor": "world",
"belief": "Wang Qiang, Li Ming, and Zhao Min all work in the same company",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narrati... |
10 | Ambiguous Story Task | Zhang Wei is the performance champion of the department, but he encounters some challenges in his recent project, which causes his performance to be not good. Li Yun is the department manager, he always supports Zhang Wei, hoping to fight for the best evaluation for him in the year-end review. Chen Tao is Zhang Wei's c... | [
{
"actor": "world",
"belief": "Zhang Wei is the performance champion of the department",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",
... |
11 | Ambiguous Story Task | Zhang Hua and Li Qiang are jointly responsible for a project, the performance of this project directly affects their promotion. Li Qiang frowns in front of the computer, the data analysis report in front of him seems to trouble him. Zhang Hua notices Li Qiang's appearance, walks over and says "I also come to learn", an... | [
{
"actor": "world",
"belief": "Zhang Hua and Li Qiang are jointly responsible for a project",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration... |
12 | Ambiguous Story Task | The project deadline approaches, and the team works overtime to ensure completion on time. Chen Jie is the project leader, he notices that Su Qing seems to lack focus recently, and Old Li needs to leave early for personal reasons. During the overtime in the evening, Chen Jie intentionally leaves a progress report on th... | [
{
"actor": "world",
"belief": "The project deadline approaches",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Action/Event",
"mental_source": "Narration",
"context": "Neutral"
... |
13 | Ambiguous Story Task | Zhang Hua is the leader of the company, Li Jun and Chen Yu are employees. The company's project is about to end, Zhang Hua and Li Jun work overtime until very late, while Chen Yu, for personal reasons, lets Li Jun help her take a leave. When it comes to rest time, Li Jun seems to mention Chen Yu unintentionally in his ... | [
{
"actor": "world",
"belief": "Zhang Hua is the leader of the company",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Identity/Relation",
"mental_source": "Narration",
"context": "N... |
14 | Ambiguous Story Task | Huang Li and Chen Jie sit in the company's rest area, they are whispering and discussing something. The office door slowly opens, Wang Qiang walks in, he seems to be looking for something, and does not hear the conversation. The conversation between Chen Jie and Huang Li suddenly stops, they quickly switch topics, and ... | [
{
"actor": "world",
"belief": "Huang Li and Chen Jie sit in the company's rest area",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Location",
"mental_source": "Narration",
"context... |
Dataset Card for OmniToM
Dataset Details
Dataset Description
OmniToM is a benchmark for evaluating Theory of Mind in language models through explicit belief-structure modeling. Instead of scoring only endpoint answers to social-reasoning questions, OmniToM exposes the intermediate belief structure that a model must build in order to reason coherently about what different actors know, believe, infer, intend, or misunderstand.
Each example is a short English story paired with:
- a set of actor-centered belief propositions
- a reserved
worldactor for narrator/world facts - a seven-dimensional schema label vector for every belief
The benchmark supports two linked tasks:
- Belief Extraction
- Given a story, extract the relevant belief structure as
(Actor, Belief, Order)tuples.
- Given a story, extract the relevant belief structure as
- Belief Labeling
- Given the story and belief tuples, label each belief along seven closed-set schema dimensions.
- Language(s): English
- License: MIT
Uses
Direct Use
OmniToM is designed for benchmark evaluation and diagnostic analysis. Suitable uses include:
- zero-shot belief extraction
- zero-shot belief labeling
- semantic-judge evaluation of extracted belief tables
- analysis of multi-actor and higher-order Theory-of-Mind reasoning
- process-sensitive evaluation beyond endpoint question answering
Out-of-Scope Use
OmniToM should not be treated as:
- a direct measure of real-world social intelligence
- a measure of embodied, interactive, or multimodal social reasoning
- a safety certification benchmark for deployed systems
- a clinical, educational, or psychological assessment tool
- a complete coverage benchmark for all possible Theory-of-Mind phenomena
Dataset Structure
Data Instances
Each line in the release file is one JSON object:
{
"story_id": 1,
"story_category": "Ambiguous Story Task",
"story": "Story text...",
"beliefs": [
{
"actor": "world",
"belief": "A minimal propositional statement.",
"labels": {
"order": "0",
"truth_status": "True",
"knowledge_access": "Public",
"representation": "Explicit",
"content_type": "Action/Event",
"mental_source": "Narration",
"context": "Neutral"
}
}
]
}
Data Fields
story_id- Unique integer identifier for the story.
story_category- One of seven retained benchmark categories.
story- Raw story text used for both extraction and labeling tasks.
beliefs- List of annotated belief propositions.
beliefs[].actor- Belief holder. The reserved actor
worlddenotes narrator/world facts.
- Belief holder. The reserved actor
beliefs[].belief- Minimal propositional belief statement.
beliefs[].labels.order- Recursive depth in
{0,1,2,3}.
- Recursive depth in
beliefs[].labels.truth_statusTrue,False, orUnknown.
beliefs[].labels.knowledge_accessPrivate,Shared, orPublic.
beliefs[].labels.representationExplicitorImplicit.
beliefs[].labels.content_type- One of:
Location,Contents/Physical State,Identity/Relation,Epistemic,Desire/Intention,Emotion,Trait/Value,Action/Event.
- One of:
beliefs[].labels.mental_source- One of:
Narration,Perception,Memory,Testimony,Inference,Imagination,Unknown.
- One of:
beliefs[].labels.contextNeutral,Temporal,Deceptive, orCounterfactual.
Data Splits
This release contains one benchmark split:
train/ benchmark split:895stories
The split is named train in the Hugging Face dataset viewer for compatibility with the default dataset loading interface. It should be interpreted as the benchmark split, not as a recommended training set.
Dataset Creation
Curation Rationale
OmniToM was created to address a limitation in prior Theory-of-Mind benchmarks for language models: most evaluate endpoint question answering rather than whether a model constructs a coherent belief representation while reading the story.
OmniToM instead evaluates explicit belief-structure modeling. The benchmark is grounded in short stories from ToMBench and organizes reasoning around an ATOMS-grounded belief-level schema for fine-grained analysis of mental-state representations.
Source Data
The benchmark sources its stories from ToMBench. From the original source corpus, OmniToM retains seven story categories whose stories provide sufficiently self-contained mental-state evidence for belief extraction from text alone:
- Ambiguous Story Task
- False Belief Task
- Faux-pas Recognition Test
- Hinting Task Test
- Persuasion Story Task
- Scalar Implicature Test
- Strange Story Task
Annotation Process
The benchmark was built with a human-validated, LLM-assisted annotation pipeline:
1,383source stories in the original corpus916stories retained after source filtering895stories released in the final benchmark22,343labeled belief propositions in the released benchmark156,401total schema labels in the released benchmark
The accompanying paper reports:
- Stage 1 expert-overlap validation after reconciliation:
83.72% - Stage 2 strict all-annotator exact-match label reliability:
92.38% - Human-human agreement on the semantic-alignment validation set:
88.86% - Human-judge agreement for the selected semantic judge:
87.76%
Who are the source data producers?
The story texts are sourced from ToMBench. The belief structures and schema labels are benchmark annotations produced through the OmniToM human-validated annotation pipeline described in the accompanying paper.
Personal and Sensitive Information
The release consists of short benchmark stories and belief annotations. It is not designed to contain personal user data, private communications, direct identifiers, medical records, or real-world sensitive records. As with many story-based datasets, names, family roles, occupations, emotions, intentions, and social situations may appear in the source material, but the benchmark is intended for research evaluation rather than identification or profiling.
Bias, Risks, and Limitations
OmniToM is story-based, text-only, English-language, and sourced from a specific upstream benchmark distribution. It therefore reflects the representational biases, writing conventions, scenario distribution, and coverage limitations of its source stories. Names, roles, social situations, and pragmatic conventions may also be unevenly distributed across categories.
Additional known limitations:
- the benchmark evaluates story-based Theory of Mind rather than interactive, embodied, or multimodal social reasoning
- the retained stories are short and self-contained, and do not stress-test long-horizon information tracking, dense temporal structure, or deeply nested mental states beyond the order-3 schema
- the released labels come from a human-validated LLM-assisted pipeline rather than fully manual annotation of every story
- the seven-dimensional schema is human-labeled and may retain interpretive subjectivity in socially ambiguous cases
- Stage 1 extraction evaluation in the paper relies on a human-validated semantic judge rather than full human adjudication across the full release
- the selected semantic judge reached
87.76%agreement with human semantic-alignment decisions, so extractionF1should be interpreted as an approximate aggregate metric rather than an exact belief-level alignment score
Recommendations
Users should interpret OmniToM as a diagnostic benchmark for explicit belief-structure modeling. Benchmark scores should not be treated as evidence of robust real-world interpersonal reasoning, embodied social competence, clinical or educational validity, or deployment safety.
Citation
@misc{omnitom2026,
title={OmniToM: Benchmarking Theory of Mind in LLMs via Explicit Belief Modeling},
author={Bawatneh, Adam and Sapkota, Sagar and Bedi, Amrit Singh and Karmaker, Santu and Shah, Mubarak},
year={2026},
eprint={2605.26322},
archivePrefix={arXiv}
}
More Information
Paper: OmniToM on arXiv
Code and evaluation scripts: Adam-12-0/omnitom-benchmark
Project page: OmniToM
- Downloads last month
- 20