Triple
T32897489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wotan’s Farewell and Magic Fire Music |
E841514
|
entity |
| Predicate | vocalTypeForWotan |
P135747
|
FINISHED |
| Object | bass-baritone |
—
|
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: bass-baritone | Statement: [Wotan’s Farewell and Magic Fire Music, vocalTypeForWotan, bass-baritone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalTypeForWotan Context triple: [Wotan’s Farewell and Magic Fire Music, vocalTypeForWotan, bass-baritone]
-
A.
vocalConfiguration
Indicates how an entity’s vocal or sound-producing characteristics are arranged or specified in relation to another entity or context.
-
B.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
C.
hasMusicalVocalType
chosen
Indicates that an entity is associated with a specific type or classification of singing voice.
-
D.
vocalCounterpartType
Indicates the type or category of a vocal counterpart relationship that one entity has to another (e.g., spoken, sung, dubbed, narrated).
-
E.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:18 a.m.