Triple
T23187397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornbostel–Sachs |
E579628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | musical instrument classification system |
C47358
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: musical instrument classification system Context triple: [Hornbostel–Sachs, instanceOf, musical instrument classification system]
-
A.
Keyboard instrument
A keyboard instrument is a musical instrument that is played by pressing keys arranged in a keyboard, which mechanically or electronically produce and control musical sounds.
-
B.
traditional musical instrument
A traditional musical instrument is a culturally rooted device, often handcrafted and passed down through generations, used to produce music that reflects the heritage and identity of a specific community or region.
-
C.
musical instrument museum
A musical instrument museum is a curated institution that collects, preserves, and exhibits historical and contemporary musical instruments to educate and inspire visitors about their cultural, technological, and artistic significance.
-
D.
musical tuning system
A musical tuning system is a structured method for assigning specific pitch frequencies to notes within a scale so that they relate to each other according to particular mathematical, acoustic, or aesthetic principles.
-
E.
keyboard music collection
A keyboard music collection is an organized set of musical works composed or arranged specifically for keyboard instruments, such as piano, harpsichord, or organ, often grouped by composer, period, style, or pedagogical purpose.
- F. None of above. chosen
Provenance (1 batch)
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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 4:05 p.m.