Triple
T2577460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | String Quartet No. 14 in C-sharp minor, Op. 131 |
E57009
|
entity |
| Predicate | fifthMovementTempo |
P38111
|
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: [String Quartet No. 14 in C-sharp minor, Op. 131, fifthMovementTempo, Presto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fifthMovementTempo Context triple: [String Quartet No. 14 in C-sharp minor, Op. 131, fifthMovementTempo, Presto]
-
A.
typicalTempoControl
Indicates that one entity serves as the usual or standard means by which the tempo of another entity (such as a process or activity) is regulated or controlled.
-
B.
hasFifthTerm
Indicates that an ordered sequence or series possesses a defined fifth element or term.
-
C.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
-
D.
fifthStation
Indicates that one entity occupies or corresponds to the fifth position in an ordered sequence, series, or arrangement relative to others.
-
E.
tempoFeature
chosen
Indicates a relationship where a musical or rhythmic element is characterized by, or associated with, a specific tempo-related property or feature.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.