Triple
T34758135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yewa dialect of Yoruba |
E1001985
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Yoruba language |
C61987
|
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 Yoruba language Context triple: [Yewa dialect of Yoruba, instanceOf, variety of Yoruba language]
-
A.
variety of Oromo language
A variety of Oromo language is a distinct regional or social form of the Oromo language characterized by unique phonological, lexical, and grammatical features while remaining mutually intelligible with other Oromo varieties.
-
B.
variety of Ewe language
A variety of Ewe language is a distinct regional or social form of the Ewe language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Ewe forms.
-
C.
regional variety of the Nupe language
A regional variety of the Nupe language is a geographically or socially defined form of Nupe that exhibits distinct phonological, lexical, or grammatical features while remaining mutually intelligible with other Nupe varieties.
-
D.
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.
-
E.
variety of Somali language
A variety of Somali language is a distinct regional or social form of Somali characterized by unique phonological, lexical, and grammatical features within the broader Somali linguistic continuum.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.