Triple
T9199125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dance of the Sugar Plum Fairy |
E220790
|
entity |
| Predicate | suiteCatalogNumber |
P85815
|
FINISHED |
| Object | Op. 71a |
—
|
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. 71a | Statement: [Dance of the Sugar Plum Fairy, suiteCatalogNumber, Op. 71a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suiteCatalogNumber Context triple: [Dance of the Sugar Plum Fairy, suiteCatalogNumber, Op. 71a]
-
A.
workCatalogueNumber
chosen
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
B.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
C.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
D.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
E.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
- 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_69ca83e8e9248190862cf3e41693b310 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd880ab808190aa785a5f1e5d5976 |
completed | April 1, 2026, 8:34 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.