Triple
T19426635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphonic Dances, Op. 45 |
E485994
|
entity |
| Predicate | hasTempoIndicationFirstMovement |
P40356
|
FINISHED |
| Object | Non allegro |
—
|
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: Non allegro | Statement: [Symphonic Dances, Op. 45, hasTempoIndicationFirstMovement, Non allegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempoIndicationFirstMovement Context triple: [Symphonic Dances, Op. 45, hasTempoIndicationFirstMovement, Non allegro]
-
A.
firstMovementTempoMarking
chosen
Indicates the tempo marking associated with the first movement of a work or composition.
-
B.
timeSignatureFirstMovement
Indicates the time signature used in the first movement of a musical work.
-
C.
hasTempoIndicationMovementMenuet
Indicates that a musical movement has a tempo marking specifying it should be played in the style or tempo of a menuet.
-
D.
hasTempoMarking
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
E.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63219f27481909fe686209defc971 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.