Triple
T25712576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet No. 2 in D major |
E644770
|
entity |
| Predicate | finaleTempoMarking |
P150104
|
FINISHED |
| Object | Andante – 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: Andante – Vivace | Statement: [String Quartet No. 2 in D major, finaleTempoMarking, Andante – Vivace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finaleTempoMarking Context triple: [String Quartet No. 2 in D major, finaleTempoMarking, Andante – Vivace]
-
A.
tempoIndicationOfFinale
chosen
Indicates that a specified tempo marking applies specifically to the finale section or final movement of a work.
-
B.
typicalTempoOfFinale
Indicates the characteristic or commonly expected tempo at which the final movement or ending section of a work is performed.
-
C.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
D.
movement3TempoMarking
Indicates the tempo marking associated specifically with the third movement of a musical work.
-
E.
fourthMovementTempoMarking
Indicates the specified tempo marking used in the fourth 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 9:17 p.m.