Triple

T30639556
Position Surface form Disambiguated ID Type / Status
Subject Lock In E779935 entity
Predicate includesFictionalTechnology P61798 FINISHED
Object threeps (personal robotic bodies) 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: threeps (personal robotic bodies) | Statement: [Lock In, includesFictionalTechnology, threeps (personal robotic bodies)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesFictionalTechnology
Context triple: [Lock In, includesFictionalTechnology, threeps (personal robotic bodies)]
  • A. featuresFictionalTechnology chosen
    Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
  • B. hasDeviceInFiction
    Indicates that an entity is depicted as possessing or using a particular device within a fictional context or work.
  • C. hasFictionalContent
    Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
  • D. hasFictionalScope
    Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
  • E. hasFictionalDeviceCapability
    Indicates that an entity possesses the ability or function associated with a particular fictional device.
  • 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_69f224a50ebc81909b961a94c7f66b12 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_6a009a0e1fa481909ed881012009b268 completed May 10, 2026, 2:45 p.m.
PD Predicate disambiguation batch_6a0092e9fcb08190a966d720684f25ec completed May 10, 2026, 2:15 p.m.
Created at: April 29, 2026, 8:29 p.m.