Triple
T37611178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WoO |
E935787
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | musical work cataloging system |
C61634
|
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 work cataloging system Context triple: [WoO, instanceOf, musical work cataloging system]
-
A.
musical work catalogue number
A musical work catalogue number is a unique identifier assigned to a specific composition within a systematic catalog of a composer’s or repertoire’s works, used to distinguish and reference pieces unambiguously.
-
B.
musical instrument classification system
A musical instrument classification system is a structured framework that categorizes instruments based on shared characteristics such as sound production method, construction, and playing technique.
-
C.
music work catalogue
chosen
A music work catalogue is an organized collection or database that systematically lists musical compositions, typically including details such as titles, composers, dates, genres, and identifying numbers for reference and management.
-
D.
musical work version
A musical work version is a distinct realization or adaptation of an underlying musical composition, differing in aspects such as arrangement, orchestration, lyrics, or performance practice while remaining recognizably derived from the same original work.
-
E.
selection of musical recordings
A selection of musical recordings is a curated collection of audio tracks chosen according to specific criteria such as genre, mood, artist, or purpose.
- 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_69f76ed0a85481909254a8a89090c826 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.