Triple

T29120279
Position Surface form Disambiguated ID Type / Status
Subject QT-1 E737159 entity
Predicate hasFictionalTechnologyContext P61798 FINISHED
Object positronic robot 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: positronic robot | Statement: [QT-1, hasFictionalTechnologyContext, positronic robot]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalTechnologyContext
Context triple: [QT-1, hasFictionalTechnologyContext, positronic robot]
  • A. featuresFictionalTechnology chosen
    Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
  • B. hasImaginedTechnologyLevel
    Indicates that an entity is associated with a specified level of technological advancement as imagined or conceptualized, rather than actually realized.
  • C. usesTechnologyInStory
    Indicates that an entity incorporates or employs a particular technology within the context of a narrative or story.
  • D. hasFictionalScope
    Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
  • E. hasFictionalFrame
    Indicates that one entity is presented or interpreted within the context of a fictional narrative, scenario, or imaginative framework provided by another entity.
  • 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_69f077ed54e08190bb02a744e8121a66 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69fd76d1e5208190a6f26651492d1e3c completed May 8, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69fd702a226c81908edfda00f4be4130 completed May 8, 2026, 5:10 a.m.
Created at: April 28, 2026, 11:25 a.m.