Triple
T25806663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Killer |
E649984
|
entity |
| Predicate | originalCoverReplaced |
P51747
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Virgin Killer, originalCoverReplaced, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCoverReplaced Context triple: [Virgin Killer, originalCoverReplaced, yes]
-
A.
formerCover
Indicates that one entity previously served as the cover (e.g., protective or outer layer) for another entity but no longer does so.
-
B.
originallyCoveredBy
Indicates that something was first protected, reported on, or documented by a particular source, medium, or entity before any others.
-
C.
originalCoverArtCensored
chosen
Indicates that the original version of the cover art has been altered, obscured, or restricted from display due to censorship.
-
D.
coverArtUpdatedFrom
Indicates that an item's cover art has been changed, using another item as the source or basis for the updated artwork.
-
E.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 22, 2026, 7:04 a.m.