Triple
T32591827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beatles (songs covered on soundtrack) |
E833091
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | compilation of cover versions |
C61744
|
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: compilation of cover versions Context triple: [The Beatles (songs covered on soundtrack), instanceOf, compilation of cover versions]
-
A.
vocal cover
A vocal cover is a performance in which a singer recreates an existing song’s vocal part, often with their own stylistic interpretation, typically recorded or performed over an instrumental or backing track.
-
B.
archival compilation album
An archival compilation album is a curated collection of previously recorded, often unreleased or rare tracks from an artist’s past sessions, performances, or catalogs, assembled and issued retrospectively for historical or fan interest.
-
C.
re-recorded albums
Re-recorded albums are music releases in which an artist newly records previously released songs, often to update sound quality, reinterpret the material, or regain control over the recordings.
-
D.
punk rock cover
A punk rock cover is a reinterpretation of an existing song performed in a fast, aggressive, and raw punk rock style, often with distorted guitars, shouted vocals, and a DIY aesthetic.
-
E.
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.
- F. None of above. chosen
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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.