Triple
T38529711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warcraft II: Battle.net Edition |
E923326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Warcraft series game |
C65538
|
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: Warcraft series game Context triple: [Warcraft II: Battle.net Edition, instanceOf, Warcraft series game]
-
A.
organization in the Warcraft universe
An organization in the Warcraft universe is a structured group of individuals, factions, or races united by a common purpose, ideology, or goal, operating within the lore’s political, military, religious, or economic landscapes.
-
B.
World of Warcraft expansion
A World of Warcraft expansion is a major content update that significantly extends the game's world, story, systems, and player progression through new zones, dungeons, raids, features, and level cap increases.
-
C.
Warcraft universe object
A Warcraft universe object is any tangible or magical entity—such as artifacts, structures, creatures, or environmental elements—originating from or existing within the lore, worlds, and cosmology of the Warcraft franchise.
-
D.
Warcraft novel
A Warcraft novel is a work of fiction set in the Warcraft universe that expands its lore, characters, and events beyond the video games through narrative storytelling.
-
E.
event in the Warcraft universe
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.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.