Triple
T30347936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Eyes of Death Perception |
E771913
|
entity |
| Predicate | userConsequence |
P75607
|
FINISHED |
| Object | distorted perception of reality |
—
|
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: distorted perception of reality | Statement: [Mystic Eyes of Death Perception, userConsequence, distorted perception of reality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userConsequence Context triple: [Mystic Eyes of Death Perception, userConsequence, distorted perception of reality]
-
A.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
B.
effectOnUser
chosen
Indicates how an action, event, or condition influences or impacts a user.
-
C.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
exploresConsequencesOf
Indicates that one entity investigates, analyzes, or examines the outcomes, implications, or effects resulting from another entity or event.
-
E.
unexpectedConsequenceOf
Indicates that one event, action, or condition occurs as an unforeseen or unintended result of another.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 7:56 p.m.