Triple
T37611849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intermezzo, Op. 118 No. 1 |
E935803
|
entity |
| Predicate | setOpusNumber |
P66233
|
FINISHED |
| Object | Op. 118 |
—
|
NE NERFINISHED |
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. 118 | Statement: [Intermezzo, Op. 118 No. 1, setOpusNumber, Op. 118]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setOpusNumber Context triple: [Intermezzo, Op. 118 No. 1, setOpusNumber, Op. 118]
-
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.
hasOpusSetTitle
Indicates that an opus (a musical or artistic work) is associated with a specific set title under which it is grouped or published.
-
C.
positionInOpus
Indicates the specific location or ordering of a part or element within a larger work or opus.
-
D.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
E.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.