Triple
T30357148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K. 183 |
E772179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | musical work identifier |
C26136
|
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 identifier Context triple: [K. 183, instanceOf, musical work identifier]
-
A.
musical work catalogue number
chosen
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.
music release identifier
A music release identifier is a unique code or label assigned to a specific music release (such as an album, single, or EP) to distinguish it from all other releases across catalogs and distribution systems.
-
C.
music identifier standard
A music identifier standard is a formalized system for uniquely labeling and cataloging musical works, recordings, and related entities to enable consistent identification, tracking, and interoperability across platforms and databases.
-
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.
musical identity
Musical identity is the evolving sense of self that individuals construct and express through their musical preferences, practices, experiences, and the social meanings attached to them.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:57 p.m.