Triple
T11251039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doom Slayer |
E266321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | id Software character |
C4830
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: id Software character Context triple: [Doom Slayer, instanceOf, id Software character]
-
A.
video game character
chosen
A video game character is a fictional, interactive entity within a game world that the player controls or encounters, defined by its abilities, appearance, behavior, and role in the game's narrative or mechanics.
-
B.
eschatological enemy leader
An eschatological enemy leader is a prophesied or symbolic antagonist who commands opposing forces in an end-times scenario, embodying ultimate resistance to divine or cosmic order.
-
C.
survivor character
A survivor character is an individual who endures and overcomes extreme adversity or life-threatening circumstances through resilience, resourcefulness, and determination.
-
D.
StarCraft II player
A StarCraft II player is an individual who strategically controls units and resources in real time to outmaneuver and defeat opponents within the game's competitive sci-fi environment.
-
E.
video game fictional entity
A video game fictional entity is any imagined character, creature, object, or construct that exists within the narrative or interactive world of a video game, defined by its designed attributes, behaviors, and role in gameplay or story.
- F. None of above.
Provenance (1 batch)
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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.