Triple
T17941463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rondo alla Turca |
E448597
|
entity |
| Predicate | usesMusicalDevice |
P60129
|
FINISHED |
| Object | percussive effects |
—
|
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: percussive effects | Statement: [Rondo alla Turca, usesMusicalDevice, percussive effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMusicalDevice Context triple: [Rondo alla Turca, usesMusicalDevice, percussive effects]
-
A.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
usesMusicalElement
chosen
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
D.
hadInstrument
Indicates that an action or event was performed using a particular instrument or tool.
-
E.
usesVocalInstrument
Indicates that an entity performs or produces sound using their voice as a musical instrument.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad95f4608190b1ebb45944218f07 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.