Triple
T37652199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omoloko |
E937202
|
entity |
| Predicate | hasRitualLeaderTitle |
P194399
|
FINISHED |
| Object | pai de santo |
—
|
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: pai de santo | Statement: [Omoloko, hasRitualLeaderTitle, pai de santo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualLeaderTitle Context triple: [Omoloko, hasRitualLeaderTitle, pai de santo]
-
A.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
B.
hasRitualName
Indicates that an entity is associated with a specific name used in a ritual or ceremonial context.
-
C.
hasRitualCustodian
Indicates that one entity serves as the designated custodian or caretaker responsible for performing, preserving, or overseeing the rituals associated with another entity.
-
D.
ritualTitle
Indicates the formal name or designation assigned to a specific ritual within a cultural, religious, or ceremonial context.
-
E.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
- F. None of above. chosen
Provenance (4 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:18 p.m.