Triple
T3930078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appetite for Destruction |
E93372
|
entity |
| Predicate | revisedCoverArt |
P15270
|
FINISHED |
| Object | cross with skulls of band members |
—
|
LITERAL FINISHED |
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: cross with skulls of band members | Statement: [Appetite for Destruction, revisedCoverArt, cross with skulls of band members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revisedCoverArt Context triple: [Appetite for Destruction, revisedCoverArt, cross with skulls of band members]
-
A.
coverArtText
Indicates that the text element is part of, or associated with, the cover art of a work.
-
B.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
-
C.
coverArtDepicts
chosen
Indicates that the subject cover art visually represents, portrays, or includes the object within its imagery.
-
D.
coverArtistFirstEdition
Indicates that an entity served as the cover artist specifically for the first edition of another work.
-
E.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
- F. None of above.
Provenance (3 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeeda7cf3c81909df30744bddbad7e |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.