Triple
T37651938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opele chain |
E937197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Yoruba divination instrument |
C64166
|
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 divination instrument Context triple: [Opele chain, instanceOf, Yoruba divination instrument]
-
A.
Yoruba musical instrument
A Yoruba musical instrument is any traditional or contemporary sound-producing device used by the Yoruba people to create music for ritual, social, or entertainment purposes, often reflecting their cultural values, rhythms, and oral traditions.
-
B.
Yoruba artwork
Yoruba artwork is a diverse body of visual and material creations—from sculpture and textiles to beadwork and ritual objects—that embody Yoruba spiritual beliefs, social values, and aesthetic principles of balance, harmony, and dynamism.
-
C.
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.
-
D.
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è.
-
E.
Igbo deity
An Igbo deity is a supernatural being within the traditional Igbo religious cosmology, embodying specific aspects of nature, morality, or community life and receiving worship, offerings, and rituals from devotees.
- 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.