Triple
T37194483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warcraft III engine |
E921556
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time strategy game engine |
C29390
|
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: real-time strategy game engine Context triple: [Warcraft III engine, instanceOf, real-time strategy game engine]
-
A.
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.
-
B.
RTS
chosen
A real-time strategy (RTS) game is a genre where players manage resources, build units and structures, and command forces in continuous time to outmaneuver and defeat opponents.
-
C.
role-playing game engine
A role-playing game engine is a software framework that provides the core systems—such as character progression, combat mechanics, dialogue, inventory, and world interaction—needed to build and run role-playing games.
-
D.
runtime engine
A runtime engine is the software component that executes compiled or interpreted code, managing program instructions, memory, and system resources during execution.
-
E.
StarCraft game structure
A StarCraft game structure is the organized framework of rules, mechanics, units, resources, and progression systems that define how players build, manage, and command their forces in competitive real-time strategy matches.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.