Triple
T28416947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto No. 2 in F minor |
E719831
|
entity |
| Predicate | hasTempoMarkingThirdMovement |
P100507
|
FINISHED |
| Object | Allegro vivace |
—
|
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 vivace | Statement: [Piano Concerto No. 2 in F minor, hasTempoMarkingThirdMovement, Allegro vivace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempoMarkingThirdMovement Context triple: [Piano Concerto No. 2 in F minor, hasTempoMarkingThirdMovement, Allegro vivace]
-
A.
tempoIndicationOfThirdMovement
Indicates the tempo marking that specifies the speed or character of the third movement in a multi-movement work.
-
B.
timeSignatureThirdMovement
Indicates the time signature used in the third movement of a musical work.
-
C.
movement3TempoMarking
chosen
Indicates the tempo marking associated specifically with the third movement of a musical work.
-
D.
fourthMovementTempoMarking
Indicates the specified tempo marking used in the fourth movement of a musical work.
-
E.
movementCountThirdSonata
Indicates the number of movements contained in a work identified as the third sonata.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 28, 2026, 1:31 a.m.