Triple
T29416790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ScummVM |
E746048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | game engine reimplementation |
C55580
|
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: game engine reimplementation Context triple: [ScummVM, instanceOf, game engine reimplementation]
-
A.
runtime engine
A runtime engine is the software component that executes compiled or interpreted code, managing program instructions, memory, and system resources during execution.
-
B.
proprietary game engine
A proprietary game engine is a privately owned, closed-source software framework used by a specific company or developer to create, run, and optimize video games, typically not licensed for public modification or broad third-party use.
-
C.
3D rendering engine
A 3D rendering engine is a software component that transforms 3D scene data—geometry, materials, lighting, and camera parameters—into 2D images or frames through processes like rasterization or ray tracing.
-
D.
3D adventure game engine
A 3D adventure game engine is a software framework that provides the tools, systems, and runtime needed to create, render, and manage interactive three-dimensional adventure games, including world building, character control, physics, scripting, and asset management.
-
E.
game development framework
A game development framework is a reusable software platform that provides tools, libraries, and structures to simplify and accelerate the creation, testing, and deployment of video games across various platforms.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:01 p.m.