Triple
T30080835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glory (2020 deluxe reissue) |
E764453
|
entity |
| Predicate | isRemasteredVersionOf |
P51502
|
FINISHED |
| Object | Glory (2016 album) |
—
|
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: Glory (2016 album) | Statement: [Glory (2020 deluxe reissue), isRemasteredVersionOf, Glory (2016 album)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemasteredVersionOf Context triple: [Glory (2020 deluxe reissue), isRemasteredVersionOf, Glory (2016 album)]
-
A.
remasteredVersion
chosen
Indicates that one entity is a newly produced, higher-quality audio or visual version of another original recording or release.
-
B.
hasRemasteredAppearanceIn
Indicates that an entity appears in a remastered version of a work or medium.
-
C.
remasteredAt
Indicates that an existing work has been reprocessed or updated at a specific time or in a specific release to improve its quality or presentation.
-
D.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
E.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:03 p.m.