Triple
T31729260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonnenflammen |
E809810
|
entity |
| Predicate | hasDramaticType |
P65429
|
FINISHED |
| Object | mythic opera |
—
|
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: mythic opera | Statement: [Sonnenflammen, hasDramaticType, mythic opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDramaticType Context triple: [Sonnenflammen, hasDramaticType, mythic opera]
-
A.
hasDramaticElements
Indicates that something contains features or qualities characteristic of drama, such as heightened emotion, tension, or conflict.
-
B.
hasDramaticStyle
chosen
Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
-
C.
hasDramaticRelief
Indicates that one entity provides or contains a moment or element that eases tension or emotional intensity within another entity or context.
-
D.
hasDramaticProduction
Indicates that an entity is associated with or features a specific dramatic production (such as a play, performance, or staged work).
-
E.
hasDramaticMedium
Indicates a relationship where a dramatic work is associated with the medium or form through which it is expressed 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:21 p.m.