Triple
T21627272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballblazer |
E533735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | one-on-one video game |
C7524
|
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: one-on-one video game Context triple: [Ballblazer, instanceOf, one-on-one video game]
-
A.
single-player video game
A single-player video game is an interactive digital experience designed for one person to play alone, focusing on individual progression, story, and challenges without requiring other human players.
-
B.
video game
chosen
A video game is an interactive digital entertainment experience in which players engage with visual and audio content through input devices to achieve goals, overcome challenges, or explore virtual worlds.
-
C.
basketball video game
A basketball video game is an interactive digital simulation that lets players control teams or individual athletes to compete in virtual basketball matches, often featuring realistic physics, official leagues, and various gameplay modes.
-
D.
table tennis video game
A table tennis video game is an interactive digital simulation of ping pong where players control paddles to hit a virtual ball across a table, aiming to outscore their opponent through timing, precision, and strategy.
-
E.
online video game service
An online video game service is a platform that delivers interactive games over the internet, enabling users to access, play, and often purchase or subscribe to games, while providing features such as matchmaking, social interaction, and digital content management.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:34 p.m.