Triple
T34704692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ijesha dialect of Yoruba |
E1000469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba dialect |
C61940
|
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: Yoruba dialect Context triple: [Ijesha dialect of Yoruba, instanceOf, Yoruba dialect]
-
A.
Igboid language
An Igboid language is any member of a subgroup of the Volta–Niger branch of the Niger–Congo language family, primarily spoken by the Igbo people and related ethnic groups in southeastern Nigeria and surrounding regions.
-
B.
Yoruba name
A Yoruba name is a culturally significant personal identifier from the Yoruba people, often derived from circumstances of birth, family lineage, religious beliefs, or aspirational meanings, and typically expressed in the Yoruba language.
-
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.
Yoruba state
A Yoruba state is a political and cultural entity historically or contemporarily governed by Yoruba people, reflecting their indigenous institutions, language, and traditions within a defined territory.
-
E.
Oshiwambo dialect
Oshiwambo dialect is a regional linguistic variety of the Oshiwambo language, characterized by distinct phonological, lexical, and grammatical features used by specific communities in northern Namibia and southern Angola.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.