Triple
T31433977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendelssohn piano concertos |
E801872
|
entity |
| Predicate | commonSoloInstrument |
P146520
|
FINISHED |
| Object | modern concert grand 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: modern concert grand piano | Statement: [Mendelssohn piano concertos, commonSoloInstrument, modern concert grand piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSoloInstrument Context triple: [Mendelssohn piano concertos, commonSoloInstrument, modern concert grand piano]
-
A.
frequentSoloInstrument
chosen
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
B.
arrangedSoloInstrument
Indicates that a musical work has been arranged specifically for performance by a single solo instrument.
-
C.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 30, 2026, 9 p.m.