Triple
T16751613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beti–Pahuin languages |
E407094
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Bantu language cluster |
C21038
|
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: Southern Bantu language cluster Context triple: [Beti–Pahuin languages, instanceOf, Southern Bantu language cluster]
-
A.
Bantu language
A Bantu language is a member of a large branch of the Niger-Congo language family, spoken primarily in central, eastern, and southern Africa, characterized by noun class systems and agglutinative morphology.
-
B.
Central Khoisan language
A Central Khoisan language is a member of the Khoisan language family spoken primarily in central southern Africa, characterized by extensive use of click consonants and complex phonological systems.
-
C.
branch of Bantu languages
chosen
A branch of Bantu languages is a subgroup within the Bantu language family whose member languages share a common historical origin and exhibit closely related grammatical, phonological, and lexical features.
-
D.
Bantu people
The Bantu people are a large, diverse group of African ethnic communities linked by related Bantu languages and shared historical origins in central and western Africa, whose migrations significantly shaped the continent’s cultural, linguistic, and demographic landscape.
-
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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.