Triple
T16429651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pursuit |
E399038
|
entity |
| Predicate | musicVideoNotedFor |
P63183
|
FINISHED |
| Object | striking 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: striking imagery | Statement: [Pursuit, musicVideoNotedFor, striking imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoNotedFor Context triple: [Pursuit, musicVideoNotedFor, striking imagery]
-
A.
musicVideoNotableFor
chosen
Indicates that a music video is especially recognized or noteworthy for a particular feature, element, or aspect.
-
B.
musicVideoNotableEvent
Indicates that a notable event is prominently featured in, associated with, or central to the context of a music video.
-
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.
musicVideoReference
Indicates that one entity is referenced, featured, or cited within the music video of another entity.
-
E.
musicVideoCameo
Indicates that one entity makes a brief or special-appearance role in the other entity’s 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fd49708190abb5065fa430eff1 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.