Triple
T36262461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wreck on the Highway |
E892126
|
entity |
| Predicate | emotionalResponseIntended |
P63081
|
FINISHED |
| Object | sorrow |
—
|
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: sorrow | Statement: [Wreck on the Highway, emotionalResponseIntended, sorrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalResponseIntended Context triple: [Wreck on the Highway, emotionalResponseIntended, sorrow]
-
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.
emotionalTrigger
Indicates that one entity causes or elicits an emotional response or reaction in another entity.
-
C.
emotionDisplayed
Indicates that an entity is outwardly expressing or showing a particular emotion.
-
D.
emotionalCounterpartOf
Indicates that one entity serves as the emotional equivalent, complement, or matching emotional role of another entity.
-
E.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
- 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_69f76e4699188190af045b11a840ce31 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b6239a40819096d61246367b612c |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.