Triple
T11376392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Doom |
E269480
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Doom series game |
C29434
|
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: Doom series game Context triple: [Final Doom, instanceOf, Doom series game]
-
A.
Doom series video game
chosen
A Doom series video game is a fast-paced, first-person shooter centered on battling demonic forces in sci-fi and hellish environments using a variety of powerful weapons and frantic, arena-style combat.
-
B.
third-person shooter series
A third-person shooter series is a collection of related video games in which players control a character viewed from a perspective outside and behind the avatar, focusing on ranged combat and action-oriented gameplay across multiple installments.
-
C.
organization in the Wolfenstein series
An organization in the Wolfenstein series is a structured faction or group—such as resistance movements, military units, or secret societies—that operates within the alternate-history setting to pursue ideological, political, or military goals that drive the narrative and conflicts of the games.
-
D.
survival horror franchise
A survival horror franchise is a series of related games, films, or media that focus on vulnerable protagonists facing terrifying threats with limited resources, emphasizing tension, fear, and strategic survival over direct combat.
-
E.
id Software game engine
An id Software game engine is a modular software framework developed by id Software that provides the core rendering, physics, input, and tooling systems used to build and run their video games.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:33 p.m.