Triple
T13607810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto, Op. 38 |
E325109
|
entity |
| Predicate | isForSoloist |
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: [Piano Concerto, Op. 38, isForSoloist, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isForSoloist Context triple: [Piano Concerto, Op. 38, isForSoloist, piano]
-
A.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
B.
soloist
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
C.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
hasNotableSoloFor
Indicates that an individual is recognized for performing a prominent or distinguished solo part within a larger work or performance associated with another entity.
-
E.
hasPianoSolo
chosen
Indicates that something includes, features, or is characterized by a piano solo 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.