Triple
T29341321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GrimE |
E744043
|
entity |
| Predicate | gameEngineType |
P166659
|
FINISHED |
| Object | proprietary engine |
—
|
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: proprietary engine | Statement: [GrimE, gameEngineType, proprietary engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineType Context triple: [GrimE, gameEngineType, proprietary engine]
-
A.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
B.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
C.
gameEngineStyle
Indicates the stylistic or design approach characteristic of a particular game engine used in creating or presenting something.
-
D.
gameEngineWork
Indicates that an entity works on, contributes to, or is employed in the development or maintenance of a game engine.
-
E.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
- F. None of above. chosen
Provenance (4 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66926e7a48190a1b580fd9fe67c31 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 1:34 p.m.