Triple
T25249537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haunted |
E632695
|
entity |
| Predicate | hasEmotionalImpact |
P84862
|
FINISHED |
| Object | haunting |
—
|
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: haunting | Statement: [Haunted, hasEmotionalImpact, haunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionalImpact Context triple: [Haunted, hasEmotionalImpact, haunting]
-
A.
hasEmotionalIntensity
Indicates that an emotion, experience, or expression is characterized by a particular degree or strength of emotional impact.
-
B.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
C.
emotionalChallenge
Indicates a situation where one entity causes or experiences significant emotional difficulty or stress in relation to another entity or circumstance.
-
D.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
E.
emotionalTrigger
chosen
Indicates that one entity causes or elicits an emotional response or reaction in another entity.
- 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:11 p.m.