Triple
T38586364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proudmoore |
E932354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Warcraft universe entity |
C65189
|
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 universe entity Context triple: [Proudmoore, instanceOf, Warcraft universe entity]
-
A.
Warcraft universe object
chosen
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.
-
B.
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.
-
C.
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.
-
D.
character from Warcraft franchise
A character from the Warcraft franchise is a fictional individual—such as a hero, villain, or supporting figure—who exists within the Warcraft universe’s lore, games, and media, possessing distinct abilities, backstory, and affiliations with its various races and factions.
-
E.
Warcraft series game
A Warcraft series game is a real-time strategy or role-playing video game set in Blizzard Entertainment’s high-fantasy Warcraft universe, featuring faction-based conflict, resource management, and story-driven campaigns.
- 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.