Triple
T7029494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodo people |
E163234
|
entity |
| Predicate | language |
P15
|
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: [Bodo people, language, Bodo language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bodo language Context triple: [Bodo people, language, 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.
Karbi language
The Karbi language is a Tibeto-Burman language spoken primarily by the Karbi people in Northeast India, especially in Assam.
-
C.
Banda-Bogbo language
The Banda-Bogbo language is a Central Sudanic language spoken by the Banda people in parts of the Central African Republic.
-
D.
Boro language
Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
-
E.
Bariai language
The Bariai language is an Austronesian language spoken by the Bariai people of New Britain in Papua New Guinea.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e200ecdc819098ca07473dfb272a |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c775919734819083beb10b4c2b146e |
completed | March 28, 2026, 6:30 a.m. |
Created at: March 27, 2026, 2:35 p.m.