Triple
T25095333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niamey Zarma |
E628572
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Zarma language |
C49435
|
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 Zarma language Context triple: [Niamey Zarma, instanceOf, variety of Zarma language]
-
A.
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.
-
B.
variety of the Berom language
A variety of the Berom language is a distinct regional or social form of Berom characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
C.
variety of the Duala language
A variety of the Duala language is a regional or social form of Duala distinguished by specific phonological, lexical, or grammatical features while remaining mutually intelligible with other Duala forms.
-
D.
variety of Lezgian language
A variety of the Lezgian language is a regional or social form of Lezgian distinguished by systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other forms.
-
E.
variety of the Uma language
A variety of the Uma language is a distinct regional or social form of Uma characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
- F. None of above. chosen
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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:24 a.m.