Triple
T34989293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shady Sands region |
E1009336
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the Fallout universe |
C63627
|
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: location in the Fallout universe Context triple: [Shady Sands region, instanceOf, location in the Fallout universe]
-
A.
Fallout 3 location
chosen
A Fallout 3 location is any distinct, explorable area within the game world—such as settlements, ruins, vaults, or landmarks—recognized by the game’s map and often containing quests, characters, enemies, or loot.
-
B.
location in The Elder Scrolls universe
A location in The Elder Scrolls universe is any distinct, explorable place—such as cities, dungeons, regions, or landmarks—within the series’ fictional world that can be visited, referenced, or interacted with in-game or in lore.
-
C.
location in the Diablo universe
A location in the Diablo universe is any distinct, lore-rich place—such as towns, dungeons, wilderness areas, or realms—where characters can explore, battle enemies, and experience story events within Sanctuary and its connected planes.
-
D.
location in Resident Evil franchise
A "location in the Resident Evil franchise" represents any distinct place or environment—such as cities, buildings, facilities, or outdoor areas—where narrative events, exploration, and encounters with enemies occur within the Resident Evil universe.
-
E.
location in The Elder Scrolls
A location in The Elder Scrolls is any distinct, explorable place within the game world—such as cities, dungeons, wilderness areas, or landmarks—defined by its geography, lore, inhabitants, and interactive elements.
- 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.