Triple
T37469812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overwatch World Cup 2019 |
E931125
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Overwatch World Cup |
C56009
|
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: Overwatch World Cup Context triple: [Overwatch World Cup 2019, instanceOf, Overwatch World Cup]
-
A.
C9 League
C9 League is a competitive, multi-tiered esports competition framework designed to organize, rank, and showcase teams within the Cloud9 ecosystem across various games and skill levels.
-
B.
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.
-
C.
Blizzard Entertainment esports league
chosen
A Blizzard Entertainment esports league is an organized, publisher-run competitive gaming structure that oversees professional play, rules, schedules, and events for Blizzard titles such as Overwatch, StarCraft, or Hearthstone.
-
D.
esports season
An esports season is a structured competitive period in which teams or players participate in a series of organized matches or tournaments within a specific game, culminating in rankings, playoffs, and often a championship event.
-
E.
StarCraft II tournament series
A StarCraft II tournament series is a recurring competitive event structure featuring organized matches between players or teams, typically spanning multiple stages and seasons, to determine champions and rankings within the StarCraft II esports scene.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.