Triple
T29028533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | III. Rondo: Allegro non troppo |
E737661
|
entity |
| Predicate | workForInstrument |
P153299
|
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: [III. Rondo: Allegro non troppo, workForInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workForInstrument Context triple: [III. Rondo: Allegro non troppo, workForInstrument, piano]
-
A.
collaboratesWithInstrument
Indicates that an entity works together or performs an activity in conjunction with a specified instrument.
-
B.
writtenForInstrument
chosen
Indicates that a work was specifically composed or arranged to be performed on a particular musical instrument.
-
C.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
D.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
E.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6600bfbf081909eb61c47571e0277 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 9:54 a.m.