Triple
T37047084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kpalsi dialect |
E916945
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Dagbani |
C64745
|
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 Dagbani Context triple: [Kpalsi dialect, instanceOf, variety of Dagbani]
-
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.
Songhay language variety
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.
-
C.
Gbe language variety
A Gbe language variety is a specific linguistic form within the Gbe continuum of closely related Niger-Congo languages spoken in parts of West Africa, distinguished by its own phonological, lexical, and grammatical features.
-
D.
variety of Wapishana language
A variety of the Wapishana language is a distinct regional or social form of Wapishana, characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other forms.
-
E.
variety of Zarma language
A variety of the Zarma language is a regional or social form of Zarma distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other Zarma 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.