Triple
T32915079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ein bürgerliches Trauerspiel |
E841984
|
entity |
| Predicate | indicatesTone |
P7344
|
FINISHED |
| Object | tragic |
—
|
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: tragic | Statement: [Ein bürgerliches Trauerspiel, indicatesTone, tragic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesTone Context triple: [Ein bürgerliches Trauerspiel, indicatesTone, tragic]
-
A.
contributesToTone
Indicates that one entity plays a role in shaping, influencing, or determining the overall tone or mood of another entity.
-
B.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
C.
isToneNeutral
Indicates that the tone of the referenced content is neither positive nor negative, but emotionally neutral or unbiased.
-
D.
haveTone
Indicates that an entity possesses or exhibits a particular tone, such as a specific attitude, mood, or quality of expression.
-
E.
tone
chosen
Indicates the characteristic attitude or emotional quality expressed in how something is communicated or presented.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:19 a.m.