Triple
T23063357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concerto in A minor, RV 356 |
E574965
|
entity |
| Predicate | finalMovementTempo |
P150104
|
FINISHED |
| Object | Presto |
—
|
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: Presto | Statement: [Concerto in A minor, RV 356, finalMovementTempo, Presto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMovementTempo Context triple: [Concerto in A minor, RV 356, finalMovementTempo, Presto]
-
A.
typicalTempoOfFinale
Indicates the characteristic or commonly expected tempo at which the final movement or ending section of a work is performed.
-
B.
tempoIndicationOfFinale
chosen
Indicates that a specified tempo marking applies specifically to the finale section or final movement of a work.
-
C.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
D.
musicalTempo
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
-
E.
finalSong
Indicates that a song is the last or concluding piece within a sequence, collection, or performance.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a1f49c81909db7e0473ec2bb1b |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.