Triple
T9430494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Violin Concerto in D major, Op. 35 |
E227360
|
entity |
| Predicate | hasCadenzaFor |
P83683
|
FINISHED |
| Object | first movement |
—
|
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: first movement | Statement: [Violin Concerto in D major, Op. 35, hasCadenzaFor, first movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCadenzaFor Context triple: [Violin Concerto in D major, Op. 35, hasCadenzaFor, first movement]
-
A.
hasCadenzaBy
Indicates that something (typically a musical work or passage) includes or is associated with a cadenza composed or authored by a specified entity.
-
B.
hasCadenza
chosen
Indicates that a musical work, passage, or performance includes or is associated with a cadenza section.
-
C.
hasOrnamentation
Indicates that an entity possesses decorative features or embellishments applied to its surface or structure.
-
D.
hasScherzo
Indicates that something (typically a musical work or movement) includes or is associated with a scherzo section or component.
-
E.
hasMelody
Indicates that one entity possesses, contains, or is characterized by a particular melody.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.