Triple
T11251138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke Nukem 3D |
E266322
|
entity |
| Predicate | engine |
P6068
|
FINISHED |
| Object | Build engine |
E914256
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Build engine | Statement: [Duke Nukem 3D, engine, Build engine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Build engine Context triple: [Duke Nukem 3D, engine, Build engine]
-
A.
Build engine
chosen
The Build engine is a 2.5D first-person shooter game engine best known for powering mid-1990s titles like Duke Nukem 3D, Blood, and Shadow Warrior.
-
B.
Velocity Engine
Velocity Engine is Apple’s marketing name for the AltiVec vector processing unit used to accelerate multimedia and scientific computations in PowerPC-based Macs.
-
C.
Builder
Builder is a creational design pattern in object-oriented programming that separates the construction of a complex object from its representation, allowing the same construction process to create different representations.
-
D.
Build Service
Build Service is an openSUSE infrastructure platform that automates building, packaging, and publishing software for multiple Linux distributions.
-
E.
NOD Engine
NOD Engine is a proprietary game engine developed by Nihilistic Software for powering their video game titles.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4f40019588190864c59e8451e80bd |
completed | April 19, 2026, 3:25 p.m. |
Created at: April 8, 2026, 9:31 p.m.