Triple

T11540993
Position Surface form Disambiguated ID Type / Status
Subject Transformers: War for Cybertron E273672 entity
Predicate hasGameEngineFeature P182 FINISHED
Object cover-based shooting elements 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: cover-based shooting elements | Statement: [Transformers: War for Cybertron, hasGameEngineFeature, cover-based shooting elements]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGameEngineFeature
Context triple: [Transformers: War for Cybertron, hasGameEngineFeature, cover-based shooting elements]
  • A. hasFeature chosen
    Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
  • B. supportsGameEngine
    Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
  • C. hasFeatureCode
    Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
  • D. hasEngineProgram
    Indicates that an entity is associated with or participates in a specific engine-related program.
  • E. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • 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_69d6aae4dfa48190a3ab0b19a159a3c5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d886deed5c81908e5c38156064f882 completed April 10, 2026, 5:13 a.m.
PD Predicate disambiguation batch_69d80879fdb48190be6dacc8aa63c809 completed April 9, 2026, 8:13 p.m.
Created at: April 8, 2026, 9:37 p.m.