Triple
T29340753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GameSpot Game of the Year 1998 |
E744029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GameSpot award |
C54855
|
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: GameSpot award Context triple: [GameSpot Game of the Year 1998, instanceOf, GameSpot award]
-
A.
The Game Awards category
The Game Awards category represents a specific area of recognition within The Game Awards ceremony, defining a set of criteria by which eligible games, creators, or performances are nominated and judged for an annual honor.
-
B.
Game Awards category
A Game Awards category is a specific classification used to group and recognize video games or industry contributors based on particular achievements, genres, or creative and technical merits during an awards event.
-
C.
Golden Joystick Awards edition
Golden Joystick Awards edition: A special version or release of a game, product, or publication that is themed around, commemorates, or is officially associated with the Golden Joystick Awards event.
-
D.
Game Developers Choice Award category
A Game Developers Choice Award category is a specific classification used to group and recognize games or individuals for particular achievements or qualities within the annual Game Developers Choice Awards.
-
E.
Counter-Strike award
A Counter-Strike award represents a specific recognition or achievement earned by a player or team for notable performance, milestones, or contributions within the Counter-Strike game or its competitive scene.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:33 p.m.