Triple
T2233656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teso language |
E49228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Nilotic language |
C6966
|
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: Eastern Nilotic language Context triple: [Teso language, instanceOf, Eastern Nilotic language]
-
A.
Nilo-Saharan language
chosen
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.
-
B.
Atlantic-Congo language
An Atlantic-Congo language is a member of a major branch of the Niger-Congo language family, encompassing a vast and diverse group of languages spoken primarily in sub-Saharan Africa.
-
C.
Chadic language
A Chadic language is any member of a branch of the Afroasiatic language family spoken primarily in parts of Nigeria, Niger, Chad, Cameroon, and neighboring regions, characterized by diverse phonological systems and complex verb morphology.
-
D.
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.
-
E.
Northern Berber language
A Northern Berber language is a member of the Berber branch of the Afroasiatic language family spoken primarily across the northern regions of North Africa, characterized by shared phonological, morphological, and syntactic features distinct from other Berber varieties.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:47 p.m.