Triple
T22410174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poison |
E553974
|
entity |
| Predicate | featuresMusicVideoTheme |
P15286
|
FINISHED |
| Object | superhero vs villain narrative |
—
|
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: superhero vs villain narrative | Statement: [Poison, featuresMusicVideoTheme, superhero vs villain narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresMusicVideoTheme Context triple: [Poison, featuresMusicVideoTheme, superhero vs villain narrative]
-
A.
musicVideoTheme
chosen
Indicates the thematic concept or subject matter that a music video is centered around or expresses.
-
B.
featuresMusicVideoParodyOf
Indicates that the music video for one work is a parody of the music video for another work.
-
C.
musicVideoFeatures
Indicates that a music video includes or prominently showcases a particular person, group, or element.
-
D.
musicVideoFrom
Indicates that a music video originates from, is derived from, or is associated with a particular source work or entity.
-
E.
musicVideoFor
Indicates that one entity is a music video created to accompany, represent, or promote another entity, typically a song or musical work.
- 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_69e11e4e6ce8819085a1e06d886bf21c |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158bb9ef88190a773d82ac9ed7a55 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.