Triple
T10154800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 6 in E minor |
E232745
|
entity |
| Predicate | hasMovementTempoIndication |
P60128
|
FINISHED |
| Object | 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: Allegro | Statement: [Symphony No. 6 in E minor, hasMovementTempoIndication, Allegro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementTempoIndication Context triple: [Symphony No. 6 in E minor, hasMovementTempoIndication, Allegro]
-
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.
fourthMovementTempoMarking
Indicates the specified tempo marking used in the fourth movement of a musical work.
-
D.
hasTempoCategory
Indicates that something is associated with a particular tempo classification or speed category.
-
E.
firstMovementTempoMarking
Indicates the tempo marking associated with the first movement of a work or composition.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec38f594819088a7eb73fc25feff |
completed | April 2, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:08 p.m.