Triple
T25286504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Remedy Entertainment |
E633956
|
entity |
| Predicate | gameEngineDeveloped |
P65183
|
FINISHED |
| Object | Northlight Engine |
—
|
NE NERFINISHED |
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: Northlight Engine | Statement: [Remedy Entertainment, gameEngineDeveloped, Northlight Engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameEngineDeveloped Context triple: [Remedy Entertainment, gameEngineDeveloped, Northlight 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.
developedEngine
chosen
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
C.
gameDevelopmentPlatform
Indicates a platform or environment used for creating, developing, and possibly deploying games.
-
D.
notableGameEngineFor
Indicates that a particular game engine is especially recognized or significant for developing or powering a given game or set of games.
-
E.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e0921ac8190a4a8fec7be7ad8f6 |
completed | May 1, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:19 p.m.