Triple
T32192334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annabelle Streator |
E822288
|
entity |
| Predicate | hasEmotionEffect |
P41794
|
FINISHED |
| Object | terror |
—
|
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: terror | Statement: [Annabelle Streator, hasEmotionEffect, terror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmotionEffect Context triple: [Annabelle Streator, hasEmotionEffect, terror]
-
A.
emotionEffect
Indicates that one entity’s emotional state causes or influences a change in another entity’s feelings, behavior, or condition.
-
B.
hasTypeOfEmotion
chosen
Indicates that an entity experiences, expresses, or is associated with a particular kind or category of emotion.
-
C.
requiresEmotion
Indicates that one entity’s occurrence, validity, or performance depends on the presence or experience of a particular emotion in another entity.
-
D.
hasEmotionalIntensity
Indicates that an emotion, experience, or expression is characterized by a particular degree or strength of emotional impact.
-
E.
hasEmote
Indicates that an entity expresses or is associated with a particular emotion or emotive expression.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bace6c508190a7b25ad1024151b6 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:35 a.m.