Triple
T12130211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osun priestesses |
E288914
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba religious office |
C10494
|
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 religious office Context triple: [Osun priestesses, instanceOf, Yoruba religious office]
-
A.
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.
-
B.
Yoruba deity
A Yoruba deity is a divine being within the Yoruba religious cosmology, embodying specific natural forces, human activities, or moral principles and serving as an intermediary between humans and the supreme god Olódùmarè.
-
C.
Yoruba religion component
chosen
A Yoruba religion component is an element of the traditional Yoruba spiritual system, such as a deity (òrìṣà), ritual practice, sacred object, or belief structure, that contributes to the cosmology, worship, and moral order of Yoruba religious life.
-
D.
Urhobo deity
An Urhobo deity is a supernatural being revered within the traditional religion of the Urhobo people of Nigeria, embodying specific aspects of nature, morality, or communal life and receiving worship through rituals, offerings, and festivals.
-
E.
Yoruba monarch
A Yoruba monarch is a traditional hereditary ruler who embodies political authority, spiritual leadership, and cultural guardianship within a Yoruba kingdom or community.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.