Triple
T27633864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Music for Piano |
E696416
|
entity |
| Predicate | isWrittenForInstrument |
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: [Music for Piano, isWrittenForInstrument, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenForInstrument Context triple: [Music for Piano, isWrittenForInstrument, piano]
-
A.
writtenForInstrument
chosen
Indicates that a work was specifically composed or arranged to be performed on a particular musical instrument.
-
B.
writtenForInstrumentFamily
Indicates that a musical work is composed or arranged specifically to be performed by a particular family of instruments.
-
C.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
D.
designedInstrument
Indicates that an agent is responsible for creating or planning the design of a particular instrument.
-
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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63125efdc819082d61f5528dcb5b4 |
completed | May 2, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:22 p.m.