Triple
T36961011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3D Realms |
E914305
|
entity |
| Predicate | notableGameEngineUsage |
P140515
|
FINISHED |
| Object | Build engine in Duke Nukem 3D |
—
|
LITERAL 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 in Duke Nukem 3D | Statement: [3D Realms, notableGameEngineUsage, Build engine in Duke Nukem 3D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameEngineUsage Context triple: [3D Realms, notableGameEngineUsage, Build engine in Duke Nukem 3D]
-
A.
notableGameEngineUse
chosen
Indicates that an entity is notably or prominently used as a game engine for another entity (such as a game or project).
-
B.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
-
C.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
D.
notableGameUsingService
Indicates that a particular game is prominently known for using or being built upon a specific service or platform.
-
E.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
- F. None of above.
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.