Triple
T37541561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bwonsamdi |
E933336
|
entity |
| Predicate | religiousRoleInLore |
P143890
|
FINISHED |
| Object | loa worshipped by trolls |
—
|
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: loa worshipped by trolls | Statement: [Bwonsamdi, religiousRoleInLore, loa worshipped by trolls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousRoleInLore Context triple: [Bwonsamdi, religiousRoleInLore, loa worshipped by trolls]
-
A.
religiousRoleInFiction
Indicates that an entity holds or performs a religious role or function within a fictional context or narrative.
-
B.
religiousAndSpiritualRole
chosen
Indicates that an entity holds or fulfills a religious or spiritual function, office, or responsibility in relation to another entity or context.
-
C.
religiousTextRole
Indicates the specific role or function that a religious text has in relation to a person, group, practice, or tradition.
-
D.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
E.
eraOfReligiousFunction
Indicates the historical time period during which a religious role, office, or function was actively performed or held.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:17 p.m.