Triple
T20696531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Haunting of Ghostly Greens |
E508674
|
entity |
| Predicate | intendedEmotionalResponse |
P63081
|
FINISHED |
| Object | fear |
—
|
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: fear | Statement: [The Haunting of Ghostly Greens, intendedEmotionalResponse, fear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEmotionalResponse Context triple: [The Haunting of Ghostly Greens, intendedEmotionalResponse, fear]
-
A.
intendedEmotion
chosen
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
-
B.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
C.
provokesEmotionType
Indicates that one entity causes or elicits a specific type of emotional response in another entity.
-
D.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
E.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
- 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_69e0b4c2b2a481909e31e9cb8f81ab55 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c1123d7c81908a1d16923437266d |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:10 p.m.