Triple
T25935486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rat On! |
E653540
|
entity |
| Predicate | coverArtReputation |
P167730
|
FINISHED |
| Object | notorious |
—
|
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: notorious | Statement: [Rat On!, coverArtReputation, notorious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverArtReputation Context triple: [Rat On!, coverArtReputation, notorious]
-
A.
coverArtStatus
Indicates the current state or condition of an item's cover art, such as whether it is present, missing, pending, or approved.
-
B.
coverArtText
Indicates that the text element is part of, or associated with, the cover art of a work.
-
C.
isCoverArtFor
Indicates that one item serves as the cover artwork or visual representation for another item, such as a publication, recording, or product.
-
D.
coverArtHomageTo
Indicates that one piece of cover art is intentionally designed as an homage or stylistic tribute to another specific cover art.
-
E.
coverArtUpdate
Indicates an action where the visual cover artwork associated with an item is changed or replaced with a new version.
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 22, 2026, 8:39 a.m.