Triple
T28796334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Tamajeq |
E727095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northern Songhay–influenced language variety |
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: Northern Songhay–influenced language variety Context triple: [Air Tamajeq, instanceOf, Northern Songhay–influenced language variety]
-
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.
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.
-
C.
regional variety of the Bambara language
A regional variety of the Bambara language is a geographically or socially defined form of Bambara that differs from other varieties in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible.
-
D.
regional variety of Koyra Chiini
A regional variety of Koyra Chiini is a geographically localized form of the Koyra Chiini language characterized by distinct phonological, lexical, or grammatical features specific to a particular area or community.
-
E.
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.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:25 a.m.