Triple
T23666583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amri Karbi |
E584594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Karbi language |
C47931
|
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 Karbi language Context triple: [Amri Karbi, instanceOf, variety of the Karbi language]
-
A.
variety of the Kaili language
A variety of the Kaili language is a distinct regional or social form of Kaili characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Kaili forms.
-
B.
variety of Kunama language
A variety of Kunama language is a distinct regional or social form of the Kunama language characterized by unique phonological, lexical, or grammatical features within the broader Kunama-speaking community.
-
C.
Yao language variety
A Yao language variety is a specific regional or social form of the Yao language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Yao linguistic continuum.
-
D.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
E.
variety of the Dinka language
A variety of the Dinka language is a specific regional or social form of Dinka distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Dinka varieties.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:50 p.m.