Triple
T30728128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata for Viola and Piano |
E782337
|
entity |
| Predicate | writtenForPerformerType |
P116845
|
FINISHED |
| Object | violist |
—
|
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: violist | Statement: [Sonata for Viola and Piano, writtenForPerformerType, violist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenForPerformerType Context triple: [Sonata for Viola and Piano, writtenForPerformerType, violist]
-
A.
writtenForPerformer
Indicates that a work was specifically composed or created to be performed by a particular performer or type of performer.
-
B.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
writtenForInstrument
Indicates that a work was specifically composed or arranged to be performed on a particular musical instrument.
-
D.
intendedForPerformanceBy
chosen
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
E.
performerDescribedAs
Indicates that a performer is characterized or referred to using a particular description, label, or role.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:37 p.m.