Triple
T37886201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 29 in B-flat major, Op. 106 "Hammerklavier" |
E944998
|
entity |
| Predicate | tempoMarkingOfFirstMovement |
P40356
|
FINISHED |
| Object | Allegro |
—
|
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: Allegro | Statement: [Piano Sonata No. 29 in B-flat major, Op. 106 "Hammerklavier", tempoMarkingOfFirstMovement, Allegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoMarkingOfFirstMovement Context triple: [Piano Sonata No. 29 in B-flat major, Op. 106 "Hammerklavier", tempoMarkingOfFirstMovement, Allegro]
-
A.
firstMovementTempoMarking
chosen
Indicates the tempo marking associated with the first movement of a work or composition.
-
B.
timeSignatureFirstMovement
Indicates the time signature used in the first movement of a musical work.
-
C.
tempoMarkingSecondMovement
Indicates the tempo marking that applies specifically to the second movement of a musical work.
-
D.
firstMovementDuration
Indicates the length of time that the first movement or initial segment of an event, work, or process lasts.
-
E.
movement3TempoMarking
Indicates the tempo marking associated specifically with the third movement of a musical work.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.