Triple
T11634075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoruba religion |
E276471
|
entity |
| Predicate | centralDivinationSystem |
P23889
|
FINISHED |
| Object | Ifa divination |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ifa divination | Statement: [Yoruba religion, centralDivinationSystem, Ifa divination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralDivinationSystem Context triple: [Yoruba religion, centralDivinationSystem, Ifa divination]
-
A.
divinationMethod
chosen
Indicates the method or technique used to perform a divinatory act or practice.
-
B.
divineSign
Indicates that one entity serves as a supernatural or sacred omen, message, or signal from a divine source to another entity.
-
C.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
D.
centralMystery
Indicates that something serves as the primary unresolved question or puzzle around which a narrative, situation, or investigation is structured.
-
E.
associatedTarotPathInSomeSystems
Indicates that, in certain interpretive or esoteric systems, one entity is linked or mapped to a particular path within the Tarot framework.
- F. None of above.
Provenance (3 batches)
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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25c0b00819095898d2b2445ecfb |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.