Triple
T2577305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fidelio, Op. 72 |
E57006
|
entity |
| Predicate | Opus number |
P37553
|
FINISHED |
| Object | Op. 72 |
—
|
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: Op. 72 | Statement: [Fidelio, Op. 72, Opus number, Op. 72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Opus number Context triple: [Fidelio, Op. 72, Opus number, Op. 72]
-
A.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
B.
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).
-
C.
numberInClassicalTradition
Indicates that an entity is associated with a specific number as defined or used within a particular classical tradition (e.g., mythology, religion, or philosophy).
-
D.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
-
E.
isNumberedBy
chosen
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.