Triple
T31534439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Scherzo: Pizzicato ostinato – Allegro (in F major) |
E804565
|
entity |
| Predicate | associatedWorkOpusNumber |
P207453
|
FINISHED |
| Object | Op. 36 |
—
|
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. 36 | Statement: [III. Scherzo: Pizzicato ostinato – Allegro (in F major), associatedWorkOpusNumber, Op. 36]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWorkOpusNumber Context triple: [III. Scherzo: Pizzicato ostinato – Allegro (in F major), associatedWorkOpusNumber, Op. 36]
-
A.
authorWorkNumber
Indicates the specific ordinal number or position of a work within an author's body of works.
-
B.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
-
C.
seriesNumberOfWorks
Indicates that an entity is assigned a specific position or sequence number within a series of related works.
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
- F. None of above. chosen
Provenance (4 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:02 p.m.