Triple
T17955443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreutzer Sonata |
E448932
|
entity |
| Predicate | hasThirdMovementTempoMarking |
P100507
|
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: [Kreutzer Sonata, hasThirdMovementTempoMarking, Presto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThirdMovementTempoMarking Context triple: [Kreutzer Sonata, hasThirdMovementTempoMarking, Presto]
-
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.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afafe814819085300163f73de5f2 |
completed | April 19, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.