Triple
T23925569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goundam dialect of Koyra Chiini |
E602341
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Songhay language |
C20743
|
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: variety of the Songhay language Context triple: [Goundam dialect of Koyra Chiini, instanceOf, variety of the Songhay language]
-
A.
Songhay language variety
chosen
A Songhay language variety is a specific regional or social form of the Songhay language continuum, distinguished by its unique phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Songhay varieties.
-
B.
Songhay language
Songhay language is a group of closely related Nilo-Saharan languages spoken primarily along the Niger River in Mali, Niger, and neighboring West African countries.
-
C.
Fula language variety
A Fula language variety is a specific regional or social form of the Fula (Fulfulde/Pulaar/Pular) language distinguished by its phonological, lexical, and grammatical features within the broader Fula continuum.
-
D.
variety of the Dinka language
A variety of the Dinka language is a specific regional or social form of Dinka distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Dinka varieties.
-
E.
Saharan language
A Saharan language is a member of a small family of related languages spoken primarily in the central Sahara region of Africa, characterized by shared grammatical structures and vocabulary distinct from neighboring language families.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:44 p.m.