Triple
T31365367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperballad |
E799993
|
entity |
| Predicate | musicVideoVisualEffects |
P16366
|
FINISHED |
| Object | computer-generated imagery |
—
|
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: computer-generated imagery | Statement: [Hyperballad, musicVideoVisualEffects, computer-generated imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoVisualEffects Context triple: [Hyperballad, musicVideoVisualEffects, computer-generated imagery]
-
A.
musicVideoTone
Indicates the prevailing emotional or stylistic mood conveyed by a music video.
-
B.
musicVideoStyle
Indicates the stylistic or aesthetic approach used in the creation or presentation of a music video.
-
C.
musicVideoProject
Indicates a relationship where an entity is involved in, associated with, or serves as a project for creating or producing a music video.
-
D.
visualEffect
chosen
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
E.
musicVideoRotation
Indicates the frequency or schedule with which a music video is played or broadcast within a given programming rotation.
- 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 29, 2026, 9:18 p.m.