Triple
T37522332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobbe Collection of historic keyboard instruments |
E932812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | musical instrument collection |
C13650
|
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 collection Context triple: [Cobbe Collection of historic keyboard instruments, instanceOf, musical instrument collection]
-
A.
musical instrument museum
chosen
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.
-
B.
musical composition collection
A musical composition collection is an organized set of related musical works, grouped together by a unifying theme, creator, period, or purpose for study, performance, or publication.
-
C.
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.
-
D.
musical instrument maker
A musical instrument maker is a craftsperson who designs, constructs, and often repairs musical instruments, combining technical skill with acoustic and artistic understanding.
-
E.
music collector
A music collector is an individual who systematically acquires, organizes, and preserves music recordings or related artifacts, often guided by specific tastes, eras, formats, or artists.
- F. None of above.
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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.