Triple
T11912740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leonore Overture No. 2 |
E283434
|
entity |
| Predicate | languageOfAssociatedOpera |
P78807
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Leonore Overture No. 2, languageOfAssociatedOpera, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAssociatedOpera Context triple: [Leonore Overture No. 2, languageOfAssociatedOpera, German]
-
A.
associatedOpera
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).
-
B.
nationalityInOpera
Indicates that an opera character or figure is portrayed as having a particular nationality within the context of the opera.
-
C.
originalLanguageOfLibretto
chosen
Indicates the language in which a libretto was originally written for a given work.
-
D.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
E.
languageOfMusic
Indicates that a specified language is used in, associated with, or characteristic of a particular piece of music or musical work.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e528f6748190ac873a040a61fa93 |
completed | April 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.