Triple
T37359675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto in A minor, Op. 85 |
E927543
|
entity |
| Predicate | hasFinaleForm |
P86650
|
FINISHED |
| Object | rondo |
—
|
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: rondo | Statement: [Piano Concerto in A minor, Op. 85, hasFinaleForm, rondo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinaleForm Context triple: [Piano Concerto in A minor, Op. 85, hasFinaleForm, rondo]
-
A.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
B.
hasFinaleMovement
Indicates that one entity (typically a musical work or performance) includes another entity as its concluding or final movement.
-
C.
finaleForm
chosen
Indicates that one entity represents the final or ultimate form, version, or stage of another entity.
-
D.
hasFinalFormLetters
Indicates that certain letters in a script change to a distinct "final" shape when they appear at the end of a word.
-
E.
hasLiveFinale
Indicates that an event, show, or series concludes with a final installment that is broadcast or performed live.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0059f4ffe481908dc500cee9051148 |
completed | May 10, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a00593a3c1881909b2ff1a29eb474b3 |
completed | May 10, 2026, 10:08 a.m. |
Created at: May 3, 2026, 4:16 p.m.