Triple
T20191012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranked Battles |
E492977
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | competitive multiplayer mode |
C10370
|
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: competitive multiplayer mode Context triple: [Ranked Battles, instanceOf, competitive multiplayer mode]
-
A.
multiplayer game
chosen
A multiplayer game is an interactive digital or physical game in which two or more players participate simultaneously or asynchronously, often collaborating or competing within a shared set of rules and objectives.
-
B.
professional gaming competition
A professional gaming competition is an organized event where skilled players or teams compete in video games for rankings, recognition, and often substantial monetary prizes under formal rules and structured formats.
-
C.
competition section
A competition section is a designated part of an event, document, or platform that organizes, presents, and manages information, rules, and results related to specific contests or competitive activities.
-
D.
Hearthstone competitive game mode
A Hearthstone competitive game mode is a structured play format where players build decks within specific rules and constraints to compete for rankings, rewards, and progression against similarly skilled opponents.
-
E.
competition shotgun
A competition shotgun is a high-performance, often semi-automatic or over-under shotgun specifically designed and tuned for speed, accuracy, and reliability in shooting sports such as 3-gun, trap, skeet, and sporting clays.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:37 p.m.