Triple
T34448299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Wheel |
E884290
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dungeons & Dragons location |
C59084
|
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: Dungeons & Dragons location Context triple: [Great Wheel, instanceOf, Dungeons & Dragons location]
-
A.
World of Warcraft location
A World of Warcraft location is any distinct in-game place—such as zones, cities, dungeons, or landmarks—defined by its geography, lore, and interactive elements within the Warcraft universe.
-
B.
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.
-
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.
Dungeons & Dragons licensed product
A Dungeons & Dragons licensed product is any officially authorized item—such as books, games, accessories, or digital content—that uses the D&D brand, settings, or rules under a formal license from its rights holder.
-
E.
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.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2 a.m.