Triple

T31490287
Position Surface form Disambiguated ID Type / Status
Subject Ortrud E803386 entity
Predicate notableAriaOrPassage P140539 FINISHED
Object invocation to the old gods in Act II 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: invocation to the old gods in Act II | Statement: [Ortrud, notableAriaOrPassage, invocation to the old gods in Act II]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableAriaOrPassage
Context triple: [Ortrud, notableAriaOrPassage, invocation to the old gods in Act II]
  • A. notableAria
    Indicates that an aria is particularly famous, distinguished, or significant within its artistic or historical context.
  • B. notableAriaAssociated chosen
    Indicates that a notable aria is associated with, or prominently linked to, a particular entity (such as a person, work, or performance).
  • C. notableBaritoneAria
    Indicates that the subject is a baritone aria recognized as particularly important, famous, or distinguished within the operatic repertoire.
  • D. notableOde
    Indicates that one entity is an ode that is notably associated with, or distinguished in relation to, another entity.
  • E. notableChorus
    Indicates that an entity is recognized for having a particularly prominent or distinguished chorus section.
  • 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_69f348ca04508190ba9379b5329dfd75 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_6a037c876524819098545e6037d3107d completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a0379e7aa0c8190bdc9ee4d54fc821b completed May 12, 2026, 7:05 p.m.
Created at: April 30, 2026, 9:37 p.m.