Triple
T9604868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Trio No. 2 in C minor, Op. 66 |
E231942
|
entity |
| Predicate | instrumentationType |
P1149
|
FINISHED |
| Object | strings and 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: strings and piano | Statement: [Piano Trio No. 2 in C minor, Op. 66, instrumentationType, strings and piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instrumentationType Context triple: [Piano Trio No. 2 in C minor, Op. 66, instrumentationType, strings and piano]
-
A.
typeOfInstrument
Indicates the specific kind or category of instrument associated with an entity.
-
B.
typicalInstrumentation
chosen
Indicates the usual or standard set of instruments commonly associated with performing or realizing something (such as a work, genre, or piece).
-
C.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
D.
instrument
Indicates that an action is carried out using a particular tool, means, or implement as its instrument.
-
E.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5e4a7c8190830b5ad9762ece46 |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.