Triple

T37888716
Position Surface form Disambiguated ID Type / Status
Subject Wintermute E945066 entity
Predicate operatesInFictionalDomain P106750 FINISHED
Object cyberspace matrix 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: cyberspace matrix | Statement: [Wintermute, operatesInFictionalDomain, cyberspace matrix]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesInFictionalDomain
Context triple: [Wintermute, operatesInFictionalDomain, cyberspace matrix]
  • A. operatesInFictionalSetting chosen
    Indicates that an entity carries out its activities or functions within a fictional or imaginary setting rather than a real-world context.
  • B. hasFictionalDomain
    Indicates that an entity is associated with or set within a fictional world, realm, or universe.
  • C. operatedByFictional
    Indicates that an entity (such as an organization, vehicle, or facility) is run, controlled, or managed by a fictional character or fictional organization.
  • D. worksInFictionalContext
    Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
  • E. isSetInFictionalUniverse
    Indicates that a narrative work takes place within a specific fictional universe or setting.
  • 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_69f76ef02668819089e7940c4001af5e completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a031e24299c81908dcbbf1b88f43dfd completed May 12, 2026, 12:33 p.m.
PD Predicate disambiguation batch_6a031ce232a48190b62bca3e94162f2f completed May 12, 2026, 12:28 p.m.
Created at: May 3, 2026, 4:19 p.m.