Triple
T23568113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resurrection Symphony |
E580024
|
entity |
| Predicate | emotionalScope |
P153193
|
FINISHED |
| Object | vast |
—
|
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: vast | Statement: [Resurrection Symphony, emotionalScope, vast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalScope Context triple: [Resurrection Symphony, emotionalScope, vast]
-
A.
emotionalCoreOf
Indicates that one entity serves as the central source, essence, or primary driver of another entity’s emotional character or experience.
-
B.
emotionalDynamic
Indicates how emotions, moods, or affective states change, interact, or influence each other between entities over time.
-
C.
emotionalTrajectory
Indicates how an entity’s emotional state changes or progresses over time in relation to another entity or context.
-
D.
emotionalFocusOf
Indicates that one entity is the primary target or center of another entity’s emotions or emotional attention.
-
E.
emotionDomain
Indicates the general emotional category or type to which a specific emotion belongs (e.g., grouping emotions into broader domains like joy, anger, or fear).
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1af6e11008190bdd28c3f85e3004e |
completed | April 29, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:35 p.m.