Triple
T7896894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unreal Engine |
E183360
|
entity |
| Predicate | notableGameEngineFor |
P79645
|
FINISHED |
| Object | high-fidelity graphics |
—
|
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: high-fidelity graphics | Statement: [Unreal Engine, notableGameEngineFor, high-fidelity graphics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameEngineFor Context triple: [Unreal Engine, notableGameEngineFor, high-fidelity graphics]
-
A.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
B.
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).
-
C.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
D.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
E.
gameDevelopmentPlatform
Indicates a platform or environment used for creating, developing, and possibly deploying 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a187a0081909a0c0822c6dab1da |
completed | March 31, 2026, 3:06 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:01 p.m.