Triple
T29654517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global StarCraft II League |
E750230
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | StarCraft II tournament series |
C56010
|
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: StarCraft II tournament series Context triple: [Global StarCraft II League, instanceOf, StarCraft II tournament series]
-
A.
StarCraft II ladder
The StarCraft II ladder is an online competitive ranking system where players are matched against others of similar skill and progress through leagues and divisions based on their game performance.
-
B.
StarCraft II player
A StarCraft II player is an individual who strategically controls units and resources in real time to outmaneuver and defeat opponents within the game's competitive sci-fi environment.
-
C.
esports arena
An esports arena is a specialized venue designed and equipped to host competitive video gaming events, featuring professional-grade gaming setups, spectator seating, large display screens, and advanced audio-visual and networking infrastructure.
-
D.
Hearthstone competition circuit
The Hearthstone competition circuit is an organized series of professional and amateur tournaments, leagues, and qualifying events where players compete in Blizzard’s digital card game for rankings, prizes, and championship titles.
-
E.
BLAST tournament circuit
The BLAST tournament circuit is a professional esports competition series, primarily for Counter-Strike, featuring structured seasonal events, high production value, and a global roster of elite teams competing for significant prize pools and rankings.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 6:54 p.m.