Triple
T37569568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egba territory |
E934649
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba region |
C31913
|
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 region Context triple: [Egba territory, instanceOf, Yoruba region]
-
A.
Yoruba sub-region
chosen
A Yoruba sub-region is a culturally and historically distinct area within the broader Yoruba homeland, characterized by shared linguistic traits, customs, political structures, and socio-economic patterns that differentiate it from other Yoruba areas.
-
B.
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.
-
C.
Igbo-speaking region
The Igbo-speaking region is a culturally and linguistically unified area in southeastern Nigeria where the Igbo language predominates and shared social, economic, and traditional practices define community life.
-
D.
Yoruba city-state
A Yoruba city-state is an autonomous urban-centered political entity historically found in southwestern Nigeria and neighboring regions, typically organized around a sacred king (oba), a complex hierarchy of chiefs, and vibrant economic, religious, and artistic institutions.
-
E.
Ijaw kingdom
The Ijaw kingdom is a traditional socio-political entity of the Ijaw people in the Niger Delta region, characterized by clan-based governance, rich maritime culture, and a history shaped by trade, resource control, and resistance to external domination.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.