Triple

T36957727
Position Surface form Disambiguated ID Type / Status
Subject Vorticons E914230 entity
Predicate gameEngineAssociation P26587 FINISHED
Object Commander Keen Galaxy engine (series context) 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: Commander Keen Galaxy engine (series context) | Statement: [Vorticons, gameEngineAssociation, Commander Keen Galaxy engine (series context)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: gameEngineAssociation
Context triple: [Vorticons, gameEngineAssociation, Commander Keen Galaxy engine (series context)]
  • A. gameEngineUsage
    Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
  • B. gameEngineType
    Indicates the type or category of game engine associated with or used by an entity.
  • C. gameEngine chosen
    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).
  • D. associatedWithGame
    Indicates that there is a relationship or connection between an entity and a particular game.
  • 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_69f76e8c498c8190b2842db80aea8b3b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fa0a7b00948190a257273d9968c5d7 completed May 5, 2026, 3:19 p.m.
PD Predicate disambiguation batch_69f9fec9c9488190ae2a349651a02782 completed May 5, 2026, 2:29 p.m.
Created at: May 3, 2026, 4:13 p.m.