Triple
T5349944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockit |
E124150
|
entity |
| Predicate | musicVideoNotableFor |
P63183
|
FINISHED |
| Object | use of robotic and disjointed mannequins |
—
|
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: use of robotic and disjointed mannequins | Statement: [Rockit, musicVideoNotableFor, use of robotic and disjointed mannequins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoNotableFor Context triple: [Rockit, musicVideoNotableFor, use of robotic and disjointed mannequins]
-
A.
musicVideoNotableEvent
Indicates that a notable event is prominently featured in, associated with, or central to the context of a music video.
-
B.
musicVideoCameo
Indicates that one entity makes a brief or special-appearance role in the other entity’s music video.
-
C.
musicVideoPremiereDate
Indicates the date on which a music video was first officially released or premiered.
-
D.
musicVideoDirector
Indicates that one entity is the director responsible for creating or overseeing the production of the other entity, which is a music video.
-
E.
hasMusicVideo
Indicates that a piece of media (typically a song) is associated with or accompanied by a music video.
- 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_69bd464be27081908807b40b75c1bbae |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd860fe4048190846a933d0e1b9386 |
completed | March 20, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69bd845c6f108190832a8d14b356368a |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2:01 p.m.