Triple
T29341631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Engine |
E744051
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | role-playing game engine |
C54864
|
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: role-playing game engine Context triple: [Infinity Engine, instanceOf, role-playing game engine]
-
A.
role‑playing game
A role-playing game is an interactive experience in which players assume fictional characters and collaboratively create or influence a narrative by making choices that affect the game world and its outcomes.
-
B.
tabletop game
A tabletop game is a structured form of play conducted on a flat surface using physical components such as boards, cards, dice, or miniatures, governed by explicit rules and typically involving two or more players.
-
C.
roguelike game
A roguelike game is a dungeon-crawling video game characterized by procedurally generated levels, turn-based gameplay, grid-based movement, and permanent character death.
-
D.
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.
-
E.
board game character
A board game character is a distinct, often themed persona or token within a board game that represents a player’s role, abilities, and progression in the game’s world and mechanics.
- 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:34 p.m.