Triple
T34989162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prydwen |
E1009333
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brotherhood of Steel asset |
C32072
|
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: Brotherhood of Steel asset Context triple: [Prydwen, instanceOf, Brotherhood of Steel asset]
-
A.
Brotherhood of Steel chapter
A Brotherhood of Steel chapter is a semi-autonomous regional division of the Brotherhood, consisting of knights, scribes, and paladins who operate under shared doctrines to secure and control advanced technology within a specific territory.
-
B.
Fallout franchise element
chosen
A Fallout franchise element is any distinct component—such as characters, factions, locations, technologies, or lore artifacts—that contributes to the post-apocalyptic world, narrative, and gameplay identity of the Fallout series.
-
C.
Relikt
A Relikt is an ancient, enduring remnant—physical, cultural, or metaphysical—that persists from a bygone era into the present, carrying with it traces of its original context and significance.
-
D.
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.
-
E.
Wolfenstein 3D episode
A Wolfenstein 3D episode is a structured collection of sequential levels within the game that share a common narrative arc, thematic setting, and progression of challenges culminating in a boss encounter.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.