Triple
T16747727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIDR |
E406998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | entertainment identifier registry |
C34933
|
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: entertainment identifier registry Context triple: [EIDR, instanceOf, entertainment identifier registry]
-
A.
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.
-
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.
persistent identifier service
chosen
A persistent identifier service is a system that creates, manages, and resolves stable, long-lasting identifiers that reliably reference digital or physical resources over time, regardless of changes to their location or metadata.
-
D.
persistent identifier service provider
A persistent identifier service provider is an organization or system that creates, manages, and resolves long-lasting, globally unique identifiers to ensure stable access to digital or physical resources over time.
-
E.
music video recording identifier
A music video recording identifier is a unique code assigned to a specific music video recording to distinguish it from other recordings and support cataloging, tracking, and reference across systems.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.