Triple
T19847649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barka Kunama |
E476910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Kunama language |
C42408
|
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 Kunama language Context triple: [Barka Kunama, instanceOf, variety of Kunama language]
-
A.
variety of the Guna language
A variety of the Guna language is a distinct regional or social form of Guna characterized by systematic differences in pronunciation, vocabulary, and grammar while remaining mutually intelligible with other Guna forms.
-
B.
variety of Fang language
A variety of Fang language is a specific regional or social form of the Fang language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Fang forms.
-
C.
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.
-
D.
Akan language variety
A specific form or dialect of the Akan language, distinguished by its unique phonological, lexical, and grammatical features used by a particular regional or social group.
-
E.
variety of Tat language
A variety of Tat language is a distinct regional or social form of the Tat language characterized by unique phonological, lexical, and grammatical features within the broader Tat-speaking community.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:51 p.m.