Triple
T6094213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sotho–Tswana languages |
E135837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Southern Bantu languages |
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 languages Context triple: [Sotho–Tswana languages, instanceOf, Southern Bantu languages]
-
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.
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.
-
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 structures and vocabulary.
-
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.
Nilo-Saharan language
A Nilo-Saharan language is a member of a proposed but controversial language family spoken primarily along the Nile and across parts of central and eastern Africa, characterized by significant internal diversity and debated genetic relationships.
- 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_69c0087cd3c48190b459848c72d84eb1 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:12 p.m.