Triple
T19669133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This Note's for You |
E472284
|
entity |
| Predicate | musicVideoControversy |
P136891
|
FINISHED |
| Object | initially banned by MTV |
—
|
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: initially banned by MTV | Statement: [This Note's for You, musicVideoControversy, initially banned by MTV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoControversy Context triple: [This Note's for You, musicVideoControversy, initially banned by MTV]
-
A.
musicVideoCameo
Indicates that one entity makes a brief or special-appearance role in the other entity’s music video.
-
B.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
-
C.
featuresMusicVideoNudity
Indicates that the music video contains depictions of nudity.
-
D.
musicVideoFrom
Indicates that a music video originates from, is derived from, or is associated with a particular source work or entity.
-
E.
musicVideoNotableEvent
Indicates that a notable event is prominently featured in, associated with, or central to the context of a music video.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416ad1b481908d2890d8c21aac5c |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.