Triple
T21864146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quema del Diablo |
E539840
|
entity |
| Predicate | hasEmotionalEffect |
P84862
|
FINISHED |
| Object | catharsis |
—
|
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: catharsis | Statement: [Quema del Diablo, hasEmotionalEffect, catharsis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionalEffect Context triple: [Quema del Diablo, hasEmotionalEffect, catharsis]
-
A.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
B.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
C.
emotionalTrigger
chosen
Indicates that one entity causes or elicits an emotional response or reaction in another entity.
-
D.
hasTypeOfEmotion
Indicates that an entity experiences, expresses, or is associated with a particular kind or category of emotion.
-
E.
requiresEmotion
Indicates that one entity’s occurrence, validity, or performance depends on the presence or experience of a particular emotion 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d63d927c8190bcfccc140357484c |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.