Triple
T11247615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skylanders: Spyro’s Adventure |
E266246
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multiplatform 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: multiplatform video game Context triple: [Skylanders: Spyro’s Adventure, instanceOf, multiplatform video game]
-
A.
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.
-
B.
platform game series
A platform game series is a collection of related video games, typically sharing characters, settings, and core mechanics, in which players navigate environments by running, jumping, and overcoming obstacles across multiple installments.
-
C.
home video game console
A home video game console is a dedicated electronic device designed to connect to a television or display and run video games using physical or digital media, typically operated with handheld controllers in a domestic setting.
-
D.
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.
-
E.
video game console hardware platform
A video game console hardware platform is a specialized computing system designed to run games and related software, defined by its architecture, performance capabilities, and compatibility with specific titles and peripherals.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.