Triple
T37456448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zerus |
E930812
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | location in the StarCraft universe |
C56011
|
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 the StarCraft universe Context triple: [Zerus, instanceOf, location in the StarCraft universe]
-
A.
location in StarCraft universe
chosen
A location in the StarCraft universe represents any distinct place—such as a planet, sector, installation, or battlefield—characterized by its lore, environment, strategic significance, and associated factions or events.
-
B.
region in the Star Wars galaxy
A region in the Star Wars galaxy is a large-scale spatial division of known space, encompassing multiple star systems, sectors, and hyperspace routes that share common political, cultural, or navigational characteristics.
-
C.
location in the Halo universe
A location in the Halo universe is any distinct, lore-recognized place—such as planets, ships, installations, or regions of space—where events, battles, or story elements occur within the Halo franchise.
-
D.
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.
-
E.
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.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.