Triple
T37874020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purge of Dalaran |
E944673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict in Warcraft lore |
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: conflict in Warcraft lore Context triple: [Purge of Dalaran, instanceOf, conflict in Warcraft lore]
-
A.
warlord conflict
A warlord conflict is a power struggle in which armed leaders, often commanding private militias, compete for territorial control, resources, and political authority in the absence or weakness of a central state.
-
B.
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.
-
C.
conflict in Tolkien legendarium
Conflict in the Tolkien legendarium is the dynamic interplay of moral, cultural, and cosmic oppositions—often embodied in wars, quests, and inner struggles—that shape the fate of Middle-earth and reveal the consequences of power, pride, and mercy.
-
D.
rank in the Warcraft universe
A rank in the Warcraft universe represents a hierarchical position or title that signifies an individual’s authority, status, and responsibilities within a specific faction, organization, or military structure.
-
E.
Warcraft race
A Warcraft race is a distinct playable or non-playable species in the Warcraft universe, defined by its unique lore, culture, abilities, and visual characteristics.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.