Triple
T36632039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bongo–Bagirmi branch |
E904348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Sudanic language subgroup |
C21223
|
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 language subgroup Context triple: [Bongo–Bagirmi branch, instanceOf, Central Sudanic language subgroup]
-
A.
Central Sudanic language
chosen
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
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.
subgroup of Niger–Congo languages
A subgroup of Niger–Congo languages is a set of closely related languages within the Niger–Congo family that share a common ancestral origin and distinctive structural and lexical features.
-
E.
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.
- 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_69f76e6c63e48190b1d0c3a79a6c7406 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.