Triple
T31880179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run Devil Run (song) |
E813859
|
entity |
| Predicate | hasSingleRelease |
P22087
|
FINISHED |
| Object | Run Devil Run (single) |
—
|
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: Run Devil Run (single) | Statement: [Run Devil Run (song), hasSingleRelease, Run Devil Run (single)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSingleRelease Context triple: [Run Devil Run (song), hasSingleRelease, Run Devil Run (single)]
-
A.
hasLiveSingleRelease
Indicates that an entity has released a live recording of a single as an official release.
-
B.
hasRelease
chosen
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
C.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
-
D.
hasBeenReleasedOn
Indicates that something has been made publicly available or launched on a specific date or platform.
-
E.
hasReleaseMedium
Indicates the medium or format through which something (such as a work or product) is released or made available.
- 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: April 30, 2026, 11:56 p.m.