Triple
T37507338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beastwarrens |
E932130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World of Warcraft zone |
C30208
|
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: World of Warcraft zone Context triple: [Beastwarrens, instanceOf, World of Warcraft zone]
-
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.
zone in World of Warcraft
chosen
A zone in World of Warcraft is a distinct geographic area within the game world featuring its own terrain, creatures, quests, and environmental theme that players can explore and interact with.
-
C.
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.
-
D.
World of Warcraft faction
A World of Warcraft faction is a large in-game organization or alliance of races, characters, and NPCs that shares a common identity, goals, and reputation system, influencing player relationships, quests, and access to resources.
-
E.
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.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.