Triple

T5619808
Position Surface form Disambiguated ID Type / Status
Subject Rangat Tehsil E147571 entity
Predicate hasOfficialLanguage P236 FINISHED
Object Kokborok E215717 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: Kokborok | Statement: [Rangat Tehsil, hasOfficialLanguage, Kokborok]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kokborok
Context triple: [Rangat Tehsil, hasOfficialLanguage, Kokborok]
  • A. Kokborok chosen
    Kokborok is a Tibeto-Burman language spoken primarily by the indigenous Tripuri people of Northeast India.
  • B. Sylheti language
    Sylheti is an Eastern Indo-Aryan language spoken primarily in the Sylhet region of Bangladesh and parts of northeastern India, closely related to Bengali but with distinct phonology, grammar, and vocabulary.
  • C. Bodo
    Bodo is a Sino-Tibetan language spoken primarily by the Bodo people in northeastern India, especially in Assam and surrounding regions.
  • D. Khowar
    Khowar is an Indo-Aryan language primarily spoken in the Chitral region of Pakistan and parts of neighboring areas, known for its rich oral tradition and distinct phonology.
  • E. Karbi language
    The Karbi language is a Tibeto-Burman language spoken primarily by the Karbi people in Northeast India, especially in Assam.
  • 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_69c00905d4588190bd967842bbcf2219 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c022108db8819098739510366adee1 completed March 22, 2026, 5:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0287fcde881908f761b701bf9a4f3 completed March 22, 2026, 5:36 p.m.
Created at: March 22, 2026, 3:40 p.m.