Triple
T8890000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glory |
E211637
|
entity |
| Predicate | coverArtUpdate |
P85556
|
FINISHED |
| Object | new cover artwork released in 2020 |
—
|
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: new cover artwork released in 2020 | Statement: [Glory, coverArtUpdate, new cover artwork released in 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverArtUpdate Context triple: [Glory, coverArtUpdate, new cover artwork released in 2020]
-
A.
coverArtText
Indicates that the text element is part of, or associated with, the cover art of a work.
-
B.
coverArtFeaturesColor
Indicates that the cover art includes or prominently displays a specific color as part of its visual design.
-
C.
coverArtDepicts
Indicates that the subject cover art visually represents, portrays, or includes the object within its imagery.
-
D.
coverArtistOf
Indicates that one entity is the artist who created the cover artwork for another entity, such as a book, album, or publication.
-
E.
hasCoverArtFeaturing
Indicates that one entity’s cover art visually features or depicts another entity.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc619188508190aacda410f0b4c98d |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:53 p.m.