Triple
T30801816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SiN (Amiga port) |
E784388
|
entity |
| Predicate | sourceGameEngine |
P159886
|
FINISHED |
| Object | Quake II 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: Quake II engine | Statement: [SiN (Amiga port), sourceGameEngine, Quake II engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceGameEngine Context triple: [SiN (Amiga port), sourceGameEngine, Quake II 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.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
C.
gameEngineType
Indicates the type or category of game engine associated with or used by an entity.
-
D.
gameEngineUsage
chosen
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
E.
gameEngineWork
Indicates that an entity works on, contributes to, or is employed in the development or maintenance of a 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 8:42 p.m.