Triple
T21627271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballblazer |
E533735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | futuristic sports video game |
C45088
|
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: futuristic sports video game Context triple: [Ballblazer, instanceOf, futuristic sports video game]
-
A.
racing video game
A racing video game is an interactive digital game where players control vehicles to compete in speed-based contests on various tracks or environments, often featuring time trials, head-to-head races, and customizable performance or visual options.
-
B.
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.
-
C.
combat racing video game
A combat racing video game is a type of racing game where players drive vehicles while using weapons, power-ups, or physical attacks to hinder opponents and gain an advantage in the race.
-
D.
motorcycle racing video game
A motorcycle racing video game is an interactive digital simulation where players control motorbikes to compete in high-speed races across various tracks, often featuring realistic physics, customizable bikes, and multiple game modes.
-
E.
video game racer
A video game racer is a player-controlled entity designed to compete in virtual racing environments, characterized by attributes like speed, handling, and acceleration that determine its performance on various tracks.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:34 p.m.