Triple

T21998983
Position Surface form Disambiguated ID Type / Status
Subject Mayurbhanj district E543275 entity
Predicate hasLanguage P15 FINISHED
Object Mundari NE NERFINISHED

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: [Mayurbhanj district, hasLanguage, Mundari]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mundari
Context triple: [Mayurbhanj district, hasLanguage, 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. Bastar Gondi
    Bastar Gondi is a regional variety of the Gondi language spoken primarily by the Gond people in the Bastar region of central India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e2c814c8190837d072789000486 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12768c0088190b0c8d5cd9b7bf710 completed April 28, 2026, 9:32 p.m.
Created at: April 16, 2026, 8:19 p.m.