Triple
T31433985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mendelssohn piano concertos |
E801872
|
entity |
| Predicate | frequentSoloists |
P86915
|
FINISHED |
| Object | concert pianists |
—
|
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: concert pianists | Statement: [Mendelssohn piano concertos, frequentSoloists, concert pianists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentSoloists Context triple: [Mendelssohn piano concertos, frequentSoloists, concert pianists]
-
A.
frequentSoloInstrument
Indicates that an instrument is commonly used as a solo instrument in performances or compositions.
-
B.
numberOfSoloists
Indicates the quantity of individual performers who play or sing solo parts within a given musical work, performance, or section.
-
C.
soloist
chosen
Indicates that an entity performs or appears alone as the primary featured performer in an artistic or musical context.
-
D.
instrumentalSoloist
Indicates that an entity performs a featured solo part on a musical instrument within a work or performance.
-
E.
vocalSoloists
Indicates that one or more entities perform as solo vocalists in a musical work 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 9 p.m.