Triple
T22437499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonatas, Op. 2 |
E554663
|
entity |
| Predicate | associatedInstrumentTechnology |
P1485
|
FINISHED |
| Object | early fortepiano |
—
|
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: early fortepiano | Statement: [Piano Sonatas, Op. 2, associatedInstrumentTechnology, early fortepiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInstrumentTechnology Context triple: [Piano Sonatas, Op. 2, associatedInstrumentTechnology, early fortepiano]
-
A.
associatedWithTechnology
chosen
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
B.
relatedInstrumentType
Indicates that one instrument is associated with or connected to another by type, such as being a variant, subtype, or closely related form.
-
C.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
D.
supportedInstrument
Indicates that an entity provides compatibility with, or operational support for, a specified instrument.
-
E.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15adf52f08190a5b592be3e68af0f |
completed | April 29, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.