Triple
T2670217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Itsekiri language |
E55729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruboid language |
C8379
|
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: Yoruboid language Context triple: [Itsekiri language, instanceOf, Yoruboid language]
-
A.
African language
chosen
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.
-
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.
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.
-
D.
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.
-
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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:54 p.m.