Triple
T31305027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Щелкунчик |
E798312
|
entity |
| Predicate | номерОпуса |
P66233
|
FINISHED |
| Object | op. 71 |
—
|
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. 71 | Statement: [Щелкунчик, номерОпуса, op. 71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: номерОпуса Context triple: [Щелкунчик, номерОпуса, op. 71]
-
A.
hasOpusNumber
chosen
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
-
B.
workNumberInSchubertCatalogue
Indicates that one entity specifies the identifying work number assigned to a composition within the Schubert catalogue for another entity.
-
C.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
D.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
-
E.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:14 p.m.