Triple
T24208268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picture to Burn |
E600457
|
entity |
| Predicate | radioEditChange |
P25064
|
FINISHED |
| Object | removal of more aggressive revenge lyric |
—
|
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: removal of more aggressive revenge lyric | Statement: [Picture to Burn, radioEditChange, removal of more aggressive revenge lyric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioEditChange Context triple: [Picture to Burn, radioEditChange, removal of more aggressive revenge lyric]
-
A.
radioEditTitle
Indicates that a title refers specifically to the radio edit version of a work, distinguishing it from other versions.
-
B.
radioSingle
Indicates that an entity is a single (individual) radio track or release, as opposed to an album, compilation, or other multi-track format.
-
C.
hasRadioEdit
chosen
Indicates that an entity has an associated radio-friendly edited version of itself.
-
D.
radioExperimentType
Indicates the specific kind or category of radio-related experiment being conducted or referenced.
-
E.
radioFormat
Indicates the specific type or style of radio programming or broadcast format associated with an entity.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f27ca7db848190952001ab2149ce62 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:52 p.m.