Triple
T12721081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owa Obokun of Ijesaland |
E303984
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba traditional ruler |
C30798
|
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 traditional ruler Context triple: [Owa Obokun of Ijesaland, instanceOf, Yoruba traditional ruler]
-
A.
Yoruba monarch
chosen
A Yoruba monarch is a traditional hereditary ruler who embodies political authority, spiritual leadership, and cultural guardianship within a Yoruba kingdom or community.
-
B.
Nigerian traditional ruler
A Nigerian traditional ruler is a culturally recognized monarch or chief who embodies ancestral authority, safeguards customs, and provides local leadership within a specific ethnic community or kingdom in Nigeria.
-
C.
Yoruba traditional authority
Yoruba traditional authority refers to the indigenous system of leadership and governance in Yoruba society, centered on kings (obas), chiefs, councils of elders, and religious institutions that regulate social order, mediate disputes, and uphold cultural norms and rituals.
-
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.
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.
- 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_69d7bdf084148190ab9d513dc0735af4 |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:24 p.m.