Triple
T23146173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonata for Tuba and Piano |
E577594
|
entity |
| Predicate | intendedInstrumentRole |
P140756
|
FINISHED |
| Object | tuba as solo instrument |
—
|
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: tuba as solo instrument | Statement: [Sonata for Tuba and Piano, intendedInstrumentRole, tuba as solo instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedInstrumentRole Context triple: [Sonata for Tuba and Piano, intendedInstrumentRole, tuba as solo instrument]
-
A.
primaryInstrumentRole
chosen
Indicates that an entity serves as the main or leading instrument in a given role, context, or performance.
-
B.
hasInstrumentRole
Indicates that an entity participates in an action or process specifically in the capacity of an instrument or means by which that action is carried out.
-
C.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
D.
reliesOnInstrument
Indicates that an action or process depends on or is carried out using a particular instrument or tool.
-
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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ece211c81908b53e98f0acae09a |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.