Triple
T38588511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle for Lordaeron |
E932399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World of Warcraft scenario |
C63938
|
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 scenario Context triple: [Battle for Lordaeron, instanceOf, World of Warcraft scenario]
-
A.
World of Warcraft game mode
A World of Warcraft game mode is a distinct ruleset or activity framework within the game that defines how players interact, progress, and compete or cooperate in specific types of content.
-
B.
World of Warcraft lore concept
A World of Warcraft lore concept is a narrative element—such as a character, faction, event, or artifact—that contributes to the overarching mythos, history, and cosmology of the Warcraft universe.
-
C.
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.
-
D.
event in the Warcraft universe
chosen
An event in the Warcraft universe is a significant occurrence or series of actions—such as battles, political upheavals, magical catastrophes, or character-driven turning points—that shapes the history, factions, and ongoing narrative of Azeroth and its connected realms.
-
E.
World of Warcraft raid
A World of Warcraft raid is a coordinated, large-group PvE activity where multiple players team up to defeat powerful bosses and complete challenging multi-encounter instances for high-level rewards.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.