Triple
T27777393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back for Good (music video) |
E699232
|
entity |
| Predicate | musicVideoForSong |
P64314
|
FINISHED |
| Object | Back for Good |
—
|
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: Back for Good | Statement: [Back for Good (music video), musicVideoForSong, Back for Good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoForSong Context triple: [Back for Good (music video), musicVideoForSong, Back for Good]
-
A.
musicVideoFor
chosen
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
-
B.
musicVideoFrom
Indicates that a music video originates from, is derived from, or is associated with a particular source work or entity.
-
C.
musicVideoRotation
Indicates the frequency or schedule with which a music video is played or broadcast within a given programming rotation.
-
D.
musicVideoReference
Indicates that one entity is referenced, featured, or cited within the music video of another entity.
-
E.
musicVideoEra
Indicates the time period or era during which a music video was produced, released, or is stylistically associated.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 5:07 p.m.