Triple
T22670187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Asylum |
E559897
|
entity |
| Predicate | notableVideo |
P18488
|
FINISHED |
| Object | Runaway Train music video |
—
|
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: Runaway Train music video | Statement: [Soul Asylum, notableVideo, Runaway Train music video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVideo Context triple: [Soul Asylum, notableVideo, Runaway Train music video]
-
A.
musicVideoNotableEvent
Indicates that a notable event is prominently featured in, associated with, or central to the context of a music video.
-
B.
musicVideoNotableFor
Indicates that a music video is especially recognized or noteworthy for a particular feature, element, or aspect.
-
C.
notableMedia
chosen
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
-
D.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
E.
notableEpisode
Indicates that a particular episode is especially significant, memorable, or noteworthy in relation to the subject.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ed50c8190a6943f51d7337b49 |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:10 p.m.