Triple

T1437519
Position Surface form Disambiguated ID Type / Status
Subject Bodo language E30589 entity
Predicate hasStandardForm P103 FINISHED
Object Standard Bodo 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: Standard Bodo | Statement: [Bodo language, hasStandardForm, Standard Bodo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Standard Bodo
Context triple: [Bodo language, hasStandardForm, Standard Bodo]
  • 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. Standard Odia
    Standard Odia is the standardized literary and official form of the Odia language used in education, administration, and formal communication.
  • C. Meitei language
    Meitei language is the principal Tibeto-Burman language of the Indian state of Manipur, serving as its official and most widely spoken tongue.
  • D. Chakma language
    The Chakma language is an Indo-Aryan language spoken primarily by the Chakma people of Bangladesh and northeastern India.
  • E. Burushaski
    Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
  • 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_69a498fc69ec8190b61722bd4b67c4d2 completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c5059ef88190af20e796acdb2058 completed March 1, 2026, 11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ad08b81a2c8190a47b1f960cf17f9d completed March 8, 2026, 5:27 a.m.
Created at: March 1, 2026, 8 p.m.