Triple
T11249440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ori series |
E266287
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | platform-adventure game series |
C10215
|
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: platform-adventure game series Context triple: [Ori series, instanceOf, platform-adventure game series]
-
A.
action-adventure game series
An action-adventure game series is a collection of related video games that blend real-time combat, exploration, and puzzle-solving within a continuous narrative universe or recurring thematic framework.
-
B.
platform game series
chosen
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.
point-and-click adventure game series
A point-and-click adventure game series is a collection of narrative-driven games where players interact with environments, characters, and puzzles primarily through mouse-based pointing and clicking to progress the story.
-
D.
arcade game series
An arcade game series is a collection of related coin-operated video games sharing common themes, characters, or gameplay mechanics, typically released over time as sequels or spin-offs.
-
E.
action role-playing game series
An action role-playing game series is a collection of related video games that blend real-time combat and character control with role-playing elements such as character progression, narrative choices, and equipment customization across multiple interconnected titles.
- 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.