Triple
T37471760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirna Scithe |
E931170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Location in World of Warcraft |
C30186
|
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 World of Warcraft Context triple: [Tirna Scithe, instanceOf, Location in World of Warcraft]
-
A.
World of Warcraft location
chosen
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 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.
-
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.
location in Hearthstone
A location in Hearthstone is a persistent, interactable card on the battlefield that occupies a board space and provides a limited-use activated effect on the controlling player's turns.
-
E.
zone in World of Warcraft
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.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.