Triple
T29028543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Rondo: Allegro non troppo |
E737661
|
entity |
| Predicate | hasPrincipalSoloInstrument |
P83294
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [III. Rondo: Allegro non troppo, hasPrincipalSoloInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrincipalSoloInstrument Context triple: [III. Rondo: Allegro non troppo, hasPrincipalSoloInstrument, piano]
-
A.
hasPrincipalOboe
Indicates that an entity (such as an orchestra or ensemble) has a designated principal oboe player associated with it.
-
B.
isKeyInstrumentFor
Indicates that one entity serves as the primary or essential instrument used to perform, enable, or achieve another entity or activity.
-
C.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
hasPianoSolo
chosen
Indicates that something includes, features, or is characterized by a piano solo performance.
-
E.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
Created at: April 28, 2026, 9:54 a.m.