Triple
T33280831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fiddle Concerto |
E852037
|
entity |
| Predicate | hasTypeOfSoloPart |
P156562
|
FINISHED |
| Object | virtuosic fiddle-style solo |
—
|
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 fiddle-style solo | Statement: [The Fiddle Concerto, hasTypeOfSoloPart, virtuosic fiddle-style solo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfSoloPart Context triple: [The Fiddle Concerto, hasTypeOfSoloPart, virtuosic fiddle-style solo]
-
A.
isSoloPartFor
Indicates that something functions as an individual or standalone component within a larger whole or composition.
-
B.
hasPianoSolo
Indicates that something includes, features, or is characterized by a piano solo performance.
-
C.
hasBassSolo
Indicates that a musical piece, section, or performance includes a solo passage specifically played by the bass instrument.
-
D.
isSoloPerformance
Indicates that the performance is carried out by a single performer without accompaniment or participation from others.
-
E.
soloPartCharacteristic
chosen
Indicates that a characteristic or property specifically applies to the solo part within a larger 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 1:32 a.m.