Triple
T37570955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoruba monarchy |
E934686
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba institution |
C30278
|
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 institution Context triple: [Yoruba monarchy, instanceOf, Yoruba institution]
-
A.
Yoruba traditional authority
chosen
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.
-
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.
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.
-
D.
Yoruba cultural event
A Yoruba cultural event is a communal gathering that showcases Yoruba traditions through music, dance, ritual, language, attire, and cuisine to celebrate heritage and reinforce social bonds.
-
E.
Urhobo culture
Urhobo culture encompasses the traditions, language, social structures, religious beliefs, arts, and customs of the Urhobo people of Nigeria’s Niger Delta, emphasizing communal life, ancestral veneration, and rich festivals.
- 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.