Triple
T6261319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On to the Next One |
E140305
|
entity |
| Predicate | musicVideoCharacteristic |
P21659
|
FINISHED |
| Object | highly stylized 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: highly stylized imagery | Statement: [On to the Next One, musicVideoCharacteristic, highly stylized imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoCharacteristic Context triple: [On to the Next One, musicVideoCharacteristic, highly stylized imagery]
-
A.
musicVideoFeatures
Indicates that a music video includes or prominently showcases a particular person, group, or element.
-
B.
musicVideoType
Indicates the specific category or format of a music video associated with a musical work or artist.
-
C.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
-
D.
musicVideoStyle
chosen
Indicates the stylistic or aesthetic approach used in the creation or presentation of a music video.
-
E.
musicVideoDirector
Indicates that one entity is the director responsible for creating or overseeing the production of the other entity, which is a music video.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063856f308190a351a661caaae5f9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.