Triple
T22878801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Concerto |
E567398
|
entity |
| Predicate | tempoIndicationOfFinale |
P150104
|
FINISHED |
| Object | Largo – Pastorale ad libitum |
—
|
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: Largo – Pastorale ad libitum | Statement: [Christmas Concerto, tempoIndicationOfFinale, Largo – Pastorale ad libitum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tempoIndicationOfFinale Context triple: [Christmas Concerto, tempoIndicationOfFinale, Largo – Pastorale ad libitum]
-
A.
typicalTempoOfFinale
Indicates the characteristic or commonly expected tempo at which the final movement or ending section of a work is performed.
-
B.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
C.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
D.
tempoIndicationOfThirdMovement
Indicates the tempo marking that specifies the speed or character of the third movement in a multi-movement work.
-
E.
tempo
Indicates the speed or pace at which an action, process, or sequence unfolds over time.
- F. None of above. chosen
Provenance (4 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5a26f4819086ede6d85a2ab2bf |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:39 p.m.