Triple
T37611396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clarinet Trio in A minor, Op. 114 |
E935792
|
entity |
| Predicate | hasKeyboardInstrument |
P24000
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [Clarinet Trio in A minor, Op. 114, hasKeyboardInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyboardInstrument Context triple: [Clarinet Trio in A minor, Op. 114, hasKeyboardInstrument, piano]
-
A.
isKeyInstrumentFor
Indicates that one entity serves as the primary or essential instrument used to perform, enable, or achieve another entity or activity.
-
B.
programmingInstrument
Indicates that an entity uses a particular instrument, tool, or device to perform a programming-related action or task.
-
C.
hasMusicalInstrument
chosen
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
D.
playedInstrument
Indicates that an entity performed or used a particular musical instrument.
-
E.
hostInstrument
Indicates that one entity serves as the instrument or platform that hosts, carries, or enables another entity or process.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:18 p.m.