Triple
T16567782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masa |
E402506
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Central Chadic language |
C3177
|
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: Central Chadic language Context triple: [Masa, instanceOf, Central Chadic language]
-
A.
Central Sudanic language
A Central Sudanic language is a member of a branch of the Nilo-Saharan language family spoken primarily in central Africa, characterized by diverse phonological systems and complex noun class or gender distinctions.
-
B.
Chadic language
chosen
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.
Southern Nilotic language
A Southern Nilotic language is a member of the Nilotic branch of the Nilo-Saharan language family spoken primarily in parts of Kenya, Tanzania, and Uganda, characterized by complex tonal systems and rich noun morphology.
-
D.
Volta–Niger language
A Volta–Niger language is a member of a proposed branch of the Niger–Congo language family spoken primarily in southern Nigeria and neighboring regions, characterized by significant lexical and grammatical diversity among its constituent languages.
-
E.
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.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:16 a.m.