Triple
T13496485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaVeyan Satanism |
E320773
|
entity |
| Predicate | viewOnDeity |
P5490
|
FINISHED |
| Object | denies existence of literal Satan |
—
|
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: denies existence of literal Satan | Statement: [LaVeyan Satanism, viewOnDeity, denies existence of literal Satan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnDeity Context triple: [LaVeyan Satanism, viewOnDeity, denies existence of literal Satan]
-
A.
viewOnOtherDeities
Indicates how one deity regards, evaluates, or conceptually relates to other deities.
-
B.
viewOnGod
Indicates a relationship where one entity holds or expresses a particular opinion, belief, or perspective about God.
-
C.
viewOfGoddess
Indicates a relationship where something visually depicts, represents, or shows an image or perspective of a goddess.
-
D.
viewOnWorship
Indicates a relationship where one entity holds a particular stance, opinion, or doctrinal position regarding the practice or concept of worship.
-
E.
viewOfGod
chosen
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4e9ca4819083116890a65389f9 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.