Triple
T30725755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farewell Symphony |
E782274
|
entity |
| Predicate | usesTempoIndication |
P60128
|
FINISHED |
| Object | Allegro assai |
—
|
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: Allegro assai | Statement: [Farewell Symphony, usesTempoIndication, Allegro assai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTempoIndication Context triple: [Farewell Symphony, usesTempoIndication, Allegro assai]
-
A.
hasTempoChanges
Indicates that the tempo of the piece or segment changes over its duration, rather than remaining constant.
-
B.
hasTempoMarking
chosen
Indicates that a musical passage, piece, or event is associated with a specific tempo indication or marking.
-
C.
hasTempoVariety
Indicates that an entity exhibits variation or changes in tempo rather than maintaining a constant speed.
-
D.
musicalTempo
Indicates the speed or pace at which a piece of music is performed or intended to be performed.
-
E.
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.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 8:36 p.m.