Triple
T2291314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taman languages |
E51509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nilo-Saharan languages |
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: Nilo-Saharan languages Context triple: [Taman languages, instanceOf, Nilo-Saharan languages]
-
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.
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.
-
C.
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.
-
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.
Mande language
A Mande language is a member of a branch of the Niger-Congo language family spoken primarily in West Africa, characterized by tonal systems, isolating morphology, and a shared historical origin among its diverse regional 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.