Triple

T9770836
Position Surface form Disambiguated ID Type / Status
Subject Dimasa E237118 entity
Predicate closelyRelatedTo P37 FINISHED
Object Bodo language E30589 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: Bodo language | Statement: [Dimasa, closelyRelatedTo, Bodo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodo language
Context triple: [Dimasa, closelyRelatedTo, Bodo language]
  • A. Bodo chosen
    Bodo is a Sino-Tibetan language spoken primarily by the Bodo people in northeastern India, especially in Assam and surrounding regions.
  • B. Bodo–Garo languages
    The Bodo–Garo languages are a branch of the Sino-Tibetan language family spoken primarily in Northeast India and neighboring regions, encompassing several related languages such as Bodo, Garo, and Dimasa.
  • C. Karbi language
    The Karbi language is a Tibeto-Burman language spoken primarily by the Karbi people in Northeast India, especially in Assam.
  • D. Banda-Bogbo language
    The Banda-Bogbo language is a Central Sudanic language spoken by the Banda people in parts of the Central African Republic.
  • E. Boro language
    Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
  • 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_69ca84d831b8819090322686b47887ce completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0f329148190a5e531478bc18073 completed April 1, 2026, 10:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1bd0cae548190a2d9b42ea4ecc372 completed April 5, 2026, 1:38 a.m.
Created at: March 30, 2026, 8:26 p.m.