Triple
T35009177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planescape |
E1009900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dungeons & Dragons campaign setting |
C58700
|
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 campaign setting Context triple: [Planescape, instanceOf, Dungeons & Dragons campaign setting]
-
A.
Dungeons & Dragons location
A Dungeons & Dragons location is a distinct, narrative-rich setting—such as a town, dungeon, wilderness, or planar realm—designed to host adventures, encounters, and exploration within the game world.
-
B.
Dungeons & Dragons licensed product
chosen
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.
-
C.
Middle-earth legendarium work
A Middle-earth legendarium work is a narrative or reference text set in J.R.R. Tolkien’s fictional world of Middle-earth, contributing to its histories, cultures, languages, and mythic events.
-
D.
MUD
A MUD (Multi-User Dungeon) is a text-based, multi-user virtual world where players interact, explore, and role-play in a shared environment, often featuring RPG-style mechanics.
-
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.