Triple
T2534250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olodumare |
E56230
|
entity |
| Predicate | veneratedThrough |
P5315
|
FINISHED |
| Object | household and communal rituals |
—
|
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: household and communal rituals | Statement: [Olodumare, veneratedThrough, household and communal rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedThrough Context triple: [Olodumare, veneratedThrough, household and communal rituals]
-
A.
veneratedFor
Indicates that one entity is highly respected, honored, or revered because of a particular quality, achievement, or characteristic of another entity.
-
B.
veneratedBy
Indicates that one entity is regarded with deep respect, reverence, or worship by another entity.
-
C.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
D.
venerationType
chosen
Indicates the specific manner or category of reverence or worship directed toward an entity.
-
E.
worshippedIn
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.