Triple
T6526130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornbostel–Sachs 314.122-4-8 |
E151305
|
entity |
| Predicate | hasInstrumentExample |
P1259
|
FINISHED |
| Object | grand 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: grand piano | Statement: [Hornbostel–Sachs 314.122-4-8, hasInstrumentExample, grand piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentExample Context triple: [Hornbostel–Sachs 314.122-4-8, hasInstrumentExample, grand piano]
-
A.
hasExample
chosen
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
B.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
C.
hasMusicalInstrument
Indicates that one entity possesses, uses, or is associated with a particular musical instrument.
-
D.
providesInstrument
Indicates that one entity supplies or makes available an instrument or tool for another entity’s use.
-
E.
alsoAppliesInstrument
Indicates that a condition, rule, or characteristic that applies to one instrument also applies to another 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ada77b448190b6e0e07494fb4dd3 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.