Triple
T11590432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 41 in C major "Jupiter" |
E274864
|
entity |
| Predicate | tempoFirstMovement |
P40356
|
FINISHED |
| Object | Allegro vivace |
—
|
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 vivace | Statement: [Symphony No. 41 in C major "Jupiter", tempoFirstMovement, Allegro vivace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoFirstMovement Context triple: [Symphony No. 41 in C major "Jupiter", tempoFirstMovement, Allegro vivace]
-
A.
timeSignatureFirstMovement
Indicates the time signature used in the first movement of a musical work.
-
B.
firstMovementTempoMarking
chosen
Indicates the tempo marking associated with the first movement of a work or composition.
-
C.
firstMovement
Indicates that an entity represents the initial or earliest movement, action, or motion in a sequence of movements.
-
D.
tempoIndicationOfThirdMovement
Indicates the tempo marking that specifies the speed or character of the third movement in a multi-movement work.
-
E.
firstMovementForm
Indicates that the subject is in the form or configuration it has during its first movement or initial phase of motion.
- 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d894643ae48190837502b713f5b9c6 |
completed | April 10, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.