Triple
T11594836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tragic Overture, Op. 81 |
E274973
|
entity |
| Predicate | hasMoodAssociation |
P48362
|
FINISHED |
| Object | tragedy |
—
|
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: tragedy | Statement: [Tragic Overture, Op. 81, hasMoodAssociation, tragedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoodAssociation Context triple: [Tragic Overture, Op. 81, hasMoodAssociation, tragedy]
-
A.
hasMood
Indicates that an entity is experiencing or characterized by a particular emotional or affective state.
-
B.
hasMoodCategory
chosen
Indicates that an entity is associated with a particular mood classification or emotional category.
-
C.
hasMoodSystem
Indicates that an entity possesses or is associated with a system responsible for managing or representing moods or emotional states.
-
D.
hasMoodDistinctions
Indicates that something differentiates or categorizes entities based on their moods or emotional states.
-
E.
supportsMood
Indicates that one entity helps maintain, enhance, or positively influence the emotional state or mood of 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8946790d08190924d60bb4b523250 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.