Triple
T30846793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charakterskizzen, Op. 40 |
E785657
|
entity |
| Predicate | pianisticFeatures |
P140124
|
FINISHED |
| Object | virtuosic writing |
—
|
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: virtuosic writing | Statement: [Charakterskizzen, Op. 40, pianisticFeatures, virtuosic writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pianisticFeatures Context triple: [Charakterskizzen, Op. 40, pianisticFeatures, virtuosic writing]
-
A.
hasPianoStyle
chosen
Indicates that one entity possesses, is associated with, or is characterized by a particular style or manner of piano playing.
-
B.
featuresElectricPiano
Indicates that something includes or makes use of an electric piano as a notable element or component.
-
C.
isPianoDriven
Indicates that something is primarily led, dominated, or characterized by the piano in its musical arrangement or performance.
-
D.
hasPianoRiff
Indicates that one entity features or contains a distinctive piano riff associated with another entity.
-
E.
hasPianist
Indicates that an entity is associated with or features a pianist, typically specifying who performs the piano part in a work, event, or group.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691784eac81909545862f67610130 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:46 p.m.