Triple
T36969455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngbaka Minagende |
E914519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Ngbaka language |
C64661
|
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 Ngbaka language Context triple: [Ngbaka Minagende, instanceOf, variety of Ngbaka language]
-
A.
Gbaya language variety
A Gbaya language variety is a specific form or dialect of the Gbaya language spoken by particular communities in Central Africa, characterized by distinct phonological, lexical, and grammatical features within the broader Gbaya language continuum.
-
B.
variety of Ngamo language
A variety of the Ngamo language is a distinct regional or social form of Ngamo characterized by its own specific phonological, lexical, and grammatical features while remaining mutually intelligible with other forms.
-
C.
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.
-
D.
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.
-
E.
Aja language variety
Aja language variety refers to any of the regional or social forms of the Aja language, a Gbe language spoken primarily in Benin and Togo, distinguished by differences in pronunciation, vocabulary, and grammar.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.