Triple
T25684974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Boro |
E644041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Boro language |
C50635
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of the Boro language Context triple: [Eastern Boro, instanceOf, variety of the Boro language]
-
A.
variety of the Berom language
A variety of the Berom language is a distinct regional or social form of Berom characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
B.
variety of the Bunun language
A variety of the Bunun language is a distinct regional or social form of Bunun characterized by systematic differences in pronunciation, vocabulary, and grammar while remaining mutually intelligible with other Bunun varieties.
-
C.
variety of the Karbi language
A variety of the Karbi language is a distinct regional or social form of Karbi characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
D.
variety of the Isnag language
A variety of the Isnag language is a regional or social form of Isnag distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
E.
Bhili language variety
A Bhili language variety is a specific regional or social form of the Bhili language, characterized by distinct phonological, lexical, and grammatical features within the broader Bhili linguistic continuum.
- F. None of above. chosen
Provenance (1 batch)
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_69e77e8046888190b07ffa58c7e2c37a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 8:06 p.m.