Triple
T4052725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viola Concerto |
E84620
|
entity |
| Predicate | dedicatedToInstrument |
P12878
|
FINISHED |
| Object | viola |
—
|
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: viola | Statement: [Viola Concerto, dedicatedToInstrument, viola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToInstrument Context triple: [Viola Concerto, dedicatedToInstrument, viola]
-
A.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
B.
inspiredInstrument
Indicates that one entity served as the creative inspiration or model for the design, creation, or development of another instrument.
-
C.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
introducedInstrument
Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
-
E.
instrumentalIn
Indicates that one entity serves as a crucial means, tool, or contributing factor in bringing about an outcome or enabling another entity’s action or effect.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb869c34819097ec3bebe402d37b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.