Triple
T10874360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia KC 33482 |
E256739
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recording catalog number |
C17831
|
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: recording catalog number Context triple: [Columbia KC 33482, instanceOf, recording catalog number]
-
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.
cataloging record
A cataloging record is a structured set of metadata describing a resource (such as a book, media item, or digital object) to enable its identification, organization, and retrieval within a catalog or information system.
-
C.
music release identifier
chosen
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.
-
D.
record company
A record company is a business entity that discovers, signs, records, promotes, and distributes music by artists and bands, typically owning or controlling the rights to those recordings.
-
E.
registry number
A registry number is a unique identifier assigned to an item, entity, or record within an official register or database to distinguish it from all others.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:21 p.m.