Triple
T22130022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardwired… to Self-Destruct |
E546881
|
entity |
| Predicate | hasMusicVideoForEverySong |
P147111
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Hardwired… to Self-Destruct, hasMusicVideoForEverySong, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicVideoForEverySong Context triple: [Hardwired… to Self-Destruct, hasMusicVideoForEverySong, true]
-
A.
hasMusicVideo
Indicates that a piece of media (typically a song) is associated with or accompanied by a music video.
-
B.
hasMusicVideoCharacteristic
Indicates that a music video possesses a specific attribute, feature, or quality.
-
C.
hasMusicVideoPerformer
Indicates that a music video features a specific performer appearing or performing in it.
-
D.
hasViralMusicVideo
Indicates that an entity possesses or is associated with a music video that has achieved viral popularity or widespread online circulation.
-
E.
musicVideoEra
Indicates the time period or era during which a music video was produced, released, or is stylistically associated.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129851db8819082d50bbb73670bf6 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:32 p.m.