Triple
T18148046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Come Undone |
E434436
|
entity |
| Predicate | hasMusicVideoCharacteristic |
P130636
|
FINISHED |
| Object | controversial |
—
|
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: controversial | Statement: [Come Undone, hasMusicVideoCharacteristic, controversial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicVideoCharacteristic Context triple: [Come Undone, hasMusicVideoCharacteristic, controversial]
-
A.
hasMusicVideo
Indicates that a piece of media (typically a song) is associated with or accompanied by a music video.
-
B.
hasMusicVideoPerformer
Indicates that a music video features a specific performer appearing or performing in it.
-
C.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
-
D.
musicVideoCameo
Indicates that one entity makes a brief or special-appearance role in the other entity’s music video.
-
E.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de360ae88190abe1ed13243e9924 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f5ae2c8190b11dee46534fa5a9 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:29 a.m.