Triple
T11093492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bongo–Bagirmi languages |
E262314
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Sudanic languages subgroup |
C11567
|
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: Central Sudanic languages subgroup Context triple: [Bongo–Bagirmi languages, instanceOf, Central Sudanic languages subgroup]
-
A.
Central Sudanic language
A Central Sudanic language is a member of a branch of the Nilo-Saharan language family spoken primarily in central Africa, characterized by diverse phonological systems and complex noun class or gender distinctions.
-
B.
Nilotic languages branch
The Nilotic languages branch is a group of related languages spoken primarily along the Nile Valley and surrounding regions of East Africa, including parts of South Sudan, Uganda, Kenya, Tanzania, and Ethiopia.
-
C.
branch of Nilo-Saharan languages
chosen
A branch of Nilo-Saharan languages is a subgroup within the proposed Nilo-Saharan language family, consisting of related languages that share common historical origins and linguistic features.
-
D.
Southern Nilotic language
A Southern Nilotic language is a member of the Nilotic branch of the Nilo-Saharan language family spoken primarily in parts of Kenya, Tanzania, and Uganda, characterized by complex tonal systems and rich noun morphology.
-
E.
Nilotic language
A Nilotic language is a member of a group of related languages spoken primarily along the Nile Valley and surrounding regions of East Africa, characterized by shared grammatical and phonological features.
- F. None of above.
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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.