Triple

T36851340
Position Surface form Disambiguated ID Type / Status
Subject King's Quest I: Quest for the Crown E910682 entity
Predicate remakeEngine P141161 FINISHED
Object Sierra's Creative Interpreter 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: Sierra's Creative Interpreter | Statement: [King's Quest I: Quest for the Crown, remakeEngine, Sierra's Creative Interpreter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: remakeEngine
Context triple: [King's Quest I: Quest for the Crown, remakeEngine, Sierra's Creative Interpreter]
  • A. remakePlatform
    Indicates that an existing work has been remade or re-released specifically for a different platform or medium.
  • B. reEnginedWith chosen
    Indicates that an existing vehicle, machine, or system has had its original engine replaced with a different specified engine.
  • C. remakeDeveloper
    Indicates that a developer is responsible for creating a new version or adaptation of an existing work (such as a game, app, or software).
  • D. remakeLanguage
    Indicates that one entity creates a new version or adaptation of another entity in a different language.
  • E. remakeFeature
    Indicates that one work is a new version or adaptation created by redoing or updating the features of an earlier work.
  • 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_69f76e8033d48190a59274f86f13be48 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9fd6834cc8190aa27153d6a99f3bb completed May 5, 2026, 2:23 p.m.
PD Predicate disambiguation batch_69f7cf7890008190a8bc355ff2d61c86 completed May 3, 2026, 10:43 p.m.
Created at: May 3, 2026, 4:13 p.m.