Triple
T12168379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bondye |
E289891
|
entity |
| Predicate | statusInPantheon |
P27705
|
FINISHED |
| Object | highest deity in Haitian Vodou |
—
|
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: highest deity in Haitian Vodou | Statement: [Bondye, statusInPantheon, highest deity in Haitian Vodou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInPantheon Context triple: [Bondye, statusInPantheon, highest deity in Haitian Vodou]
-
A.
positionInPantheon
chosen
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
-
B.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
C.
statusInTOS
Indicates the status or condition of something as defined or specified within a Terms of Service agreement.
-
D.
convertedToPantheon
Indicates that something has been transformed or repurposed into a pantheon, typically changing its function or status to that of a sacred or monumental temple.
-
E.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.