Triple
T25199896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I’ll Keep Coming |
E631096
|
entity |
| Predicate | usedInVideoGame |
P115844
|
FINISHED |
| Object | Death Stranding |
—
|
NE NERFINISHED |
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: Death Stranding | Statement: [I’ll Keep Coming, usedInVideoGame, Death Stranding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInVideoGame Context triple: [I’ll Keep Coming, usedInVideoGame, Death Stranding]
-
A.
appearedInVideoGame
chosen
Indicates that an entity is featured as a character, element, or content within a specific video game.
-
B.
videoGame
Indicates that one entity is a video game associated with, created by, or otherwise related to another entity.
-
C.
developerOfGameUsed
Indicates that an entity is the developer of a game that is (or was) used or played in a given context.
-
D.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
-
E.
inspiredVideoGame
Indicates that one entity served as the creative basis or influence for the development or design of a video game.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 12:51 p.m.