Triple

T13484880
Position Surface form Disambiguated ID Type / Status
Subject Chaibasa E318469 entity
Predicate regionalLanguage P237 FINISHED
Object Mundari E201634 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mundari | Statement: [Chaibasa, regionalLanguage, Mundari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mundari
Context triple: [Chaibasa, regionalLanguage, Mundari]
  • A. Mundari
    The Mundari are a Nilotic ethnic group of South Sudan known for their cattle-herding culture and pastoralist lifestyle.
  • B. Mundari chosen
    Mundari is an Austroasiatic Munda language of eastern India, spoken primarily by the Munda people in states such as Jharkhand, Odisha, and West Bengal.
  • C. Munduruku
    Munduruku is an indigenous people of the Brazilian Amazon known for their distinct language, rich cultural traditions, and historical prominence along the Tapajós River.
  • D. Munduruku language
    The Munduruku language is an indigenous Tupian language spoken by the Munduruku people of the Amazon region in Brazil.
  • E. Muria language
    Muria language is a Central Dravidian language spoken primarily by the Muria Gond tribal communities in central India, especially in parts of Chhattisgarh and Maharashtra.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d806b6bfec819089222715b2e86c8e completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf3a15b48190b63fb59e926a97ae completed April 12, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7463715dc8190a70a17b3ea661006 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:42 p.m.