Triple
T37898597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 15 in D major, Op. 28 "Pastoral" |
E945345
|
entity |
| Predicate | opusWithin |
P40364
|
FINISHED |
| Object | Beethoven Opus 28 |
—
|
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: Beethoven Opus 28 | Statement: [Piano Sonata No. 15 in D major, Op. 28 "Pastoral", opusWithin, Beethoven Opus 28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusWithin Context triple: [Piano Sonata No. 15 in D major, Op. 28 "Pastoral", opusWithin, Beethoven Opus 28]
-
A.
opusCategory
Indicates the classification or type of an artistic or literary work within a broader catalog or body of works.
-
B.
opusWithoutNumber
Indicates that a musical work is not assigned an official opus number in its cataloging or publication.
-
C.
opusGroup
chosen
Indicates a grouping relationship that associates individual works or compositions into a larger collective opus or set.
-
D.
opusPosition
Indicates the position or number assigned to a work within a creator’s catalog or opus sequence.
-
E.
opusNumber
Indicates that a creative work is assigned a specific opus number identifying its place within a creator’s catalog or chronological sequence of works.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.