Triple
T33364666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stairsteps – 2nd Resurrection |
E854316
|
entity |
| Predicate | hasArtistCreditNameOnCover |
P194769
|
FINISHED |
| Object | The Stairsteps |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: The Stairsteps | Statement: [Stairsteps – 2nd Resurrection, hasArtistCreditNameOnCover, The Stairsteps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtistCreditNameOnCover Context triple: [Stairsteps – 2nd Resurrection, hasArtistCreditNameOnCover, The Stairsteps]
-
A.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
B.
coverOfArtist
Indicates that one entity is a cover version of a musical work originally performed or recorded by the specified artist.
-
C.
coverArtistOf
Indicates that one entity is the artist who created the cover artwork for another entity, such as a book, album, or publication.
-
D.
hasAuthorNameOnCover
Indicates that the name of the author is printed or displayed on the cover of the work.
-
E.
isCoverArtFor
Indicates that one item serves as the cover artwork or visual representation for another item, such as a publication, recording, or product.
- F. None of above. chosen
Provenance (4 batches)
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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: May 1, 2026, 1:34 a.m.