Triple
T37413414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 466 |
E929633
|
entity |
| Predicate | hasCadenzaTradition |
P136192
|
FINISHED |
| Object | multiple cadenzas by later composers |
—
|
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: multiple cadenzas by later composers | Statement: [K. 466, hasCadenzaTradition, multiple cadenzas by later composers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadenzaTradition Context triple: [K. 466, hasCadenzaTradition, multiple cadenzas by later composers]
-
A.
hasCadenza
Indicates that a musical work, passage, or performance includes or is associated with a cadenza section.
-
B.
hasCadenzaBy
Indicates that something (typically a musical work or passage) includes or is associated with a cadenza composed or authored by a specified entity.
-
C.
hasCadenzaOptions
chosen
Indicates that an entity is associated with one or more available cadenza choices or variants.
-
D.
hasExpressiveRubatoTradition
Indicates that a musical performance practice or style is characterized by a recognized tradition of expressive tempo flexibility (rubato).
-
E.
hasEndTradition
Indicates that an entity marks or represents the concluding part or final phase of a tradition.
- 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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: May 3, 2026, 4:16 p.m.