Triple
T12894629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto for the Left Hand, Op. 17 |
E308459
|
entity |
| Predicate | pianoPart |
P21695
|
FINISHED |
| Object | left hand only |
—
|
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: left hand only | Statement: [Piano Concerto for the Left Hand, Op. 17, pianoPart, left hand only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pianoPart Context triple: [Piano Concerto for the Left Hand, Op. 17, pianoPart, left hand only]
-
A.
hasPianoAccompaniment
Indicates that something (such as a musical work or performance) is accompanied by a piano part.
-
B.
partOfMusical
chosen
Indicates that something is a component, segment, or element belonging to a larger musical work or performance.
-
C.
hasPianoArrangement
Indicates that one entity has a version or adaptation of it arranged specifically for piano.
-
D.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
E.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971484aa08190a8adfafabe600903 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.