Triple
T3991579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beti languages |
E87001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Bantu language group |
C3817
|
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 group Context triple: [Beti languages, instanceOf, Southern Bantu language group]
-
A.
Bantu language
chosen
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.
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.
-
C.
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.
-
D.
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 structures and vocabulary.
-
E.
African language
An African language is any of the diverse indigenous or historically rooted languages spoken across the African continent, encompassing numerous families such as Niger-Congo, Afroasiatic, Nilo-Saharan, and Khoisan.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.