Triple
T30815156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in Fis-moll |
E784754
|
entity |
| Predicate | firstViolinSoloRole |
P150913
|
FINISHED |
| Object | prominent in final 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: prominent in final movement | Statement: [Sinfonie in Fis-moll, firstViolinSoloRole, prominent in final movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstViolinSoloRole Context triple: [Sinfonie in Fis-moll, firstViolinSoloRole, prominent in final movement]
-
A.
principalViolin
chosen
Indicates that an entity serves as the lead or primary violin in a musical ensemble or context.
-
B.
soloistRole
Indicates that an entity has the role of performing as a soloist within a work, event, or performance.
-
C.
primaryInstrumentRole
Indicates that an entity serves as the main or leading instrument in a given role, context, or performance.
-
D.
onlyViolinConcertoBy
Indicates that the related work is the sole violin concerto composed by the specified creator.
-
E.
firstMovement
Indicates that an entity represents the initial or earliest movement, action, or motion in a sequence of movements.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: April 29, 2026, 8:43 p.m.