Triple
T36957391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation: Eisenfaust |
E914222
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wolfenstein 3D episode |
C62378
|
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: Wolfenstein 3D episode Context triple: [Operation: Eisenfaust, instanceOf, Wolfenstein 3D episode]
-
A.
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.
-
B.
Half-Life series game
A Half-Life series game is a first-person action-adventure video game set in a science fiction universe that combines narrative-driven exploration, environmental puzzles, and combat against both alien and human enemies.
-
C.
Doom series video game
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.
-
D.
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.
-
E.
fortress commander
A fortress commander is the strategic leader responsible for organizing, directing, and safeguarding a fortified stronghold and its defenders against all forms of attack.
- F. None of above. chosen
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.