Triple
T33198833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One More Angel in Heaven |
E849843
|
entity |
| Predicate | basedOnEmotion |
P197676
|
FINISHED |
| Object | mock grief |
—
|
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: mock grief | Statement: [One More Angel in Heaven, basedOnEmotion, mock grief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEmotion Context triple: [One More Angel in Heaven, basedOnEmotion, mock grief]
-
A.
intendedEmotion
Indicates the emotion that an action, expression, or communication is meant to evoke in its target, regardless of the actual emotion experienced.
-
B.
requiresEmotion
Indicates that one entity’s occurrence, validity, or performance depends on the presence or experience of a particular emotion in another entity.
-
C.
emotionalFocusOf
Indicates that one entity is the primary target or center of another entity’s emotions or emotional attention.
-
D.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
E.
emotionPersonified
Indicates that an abstract emotion is represented or depicted as if it were a person or human-like agent.
- F. None of above. chosen
Provenance (4 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 1, 2026, 1:29 a.m.