Triple
T35013689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grahtwood |
E1009997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Location in The Elder Scrolls Online |
C32075
|
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 Elder Scrolls Online Context triple: [Grahtwood, instanceOf, Location in The Elder Scrolls Online]
-
A.
location in The Elder Scrolls
chosen
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.
-
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.
character in The Elder Scrolls
A character in The Elder Scrolls is an individual entity within the game world, defined by attributes, skills, race, background, and interactive roles in the series’ narrative and gameplay.
-
D.
location in Warcraft universe
A location in the Warcraft universe is any distinct, named place—such as a city, region, dungeon, or landmark—within Azeroth or its connected realms that provides geographical context, lore significance, and gameplay functions.
-
E.
location in the Warcraft universe
A location in the Warcraft universe is any distinct, lore-defined place—ranging from continents and kingdoms to cities, dungeons, and landmarks—within Azeroth and its connected realms that serves as a setting for events, quests, and stories.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.