Triple
T31490404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridal Chorus |
E803389
|
entity |
| Predicate | sectionOfOpera |
P30380
|
FINISHED |
| Object | wedding scene of Elsa and Lohengrin |
—
|
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: wedding scene of Elsa and Lohengrin | Statement: [Bridal Chorus, sectionOfOpera, wedding scene of Elsa and Lohengrin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionOfOpera Context triple: [Bridal Chorus, sectionOfOpera, wedding scene of Elsa and Lohengrin]
-
A.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
B.
inOperaRepertoire
Indicates that a musical work is included as part of the standard or active repertoire performed in opera productions.
-
C.
partOfTheatre
Indicates that one entity is a component, section, or subdivision of a theatre.
-
D.
associatedOpera
chosen
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
E.
containsOperaticSectionSungBy
Indicates that a larger musical work or piece includes an operatic section that is performed vocally by the specified person or group.
- 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_69f6a1e4ca4881908146cb7b170209d6 |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:38 p.m.