Triple
T6922321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadaksahak language |
E160217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Songhay language |
C6446
|
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: Northern Songhay language Context triple: [Tadaksahak language, instanceOf, Northern Songhay language]
-
A.
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.
-
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.
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.
-
E.
Northern Berber language
chosen
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_69c6884d350081908d8a970e4d40ad78 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:26 p.m.