Triple

T13105112
Position Surface form Disambiguated ID Type / Status
Subject San Angeles E310823 entity
Predicate hasTechnologyInFiction P61798 FINISHED
Object voice-activated systems 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: voice-activated systems | Statement: [San Angeles, hasTechnologyInFiction, voice-activated systems]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTechnologyInFiction
Context triple: [San Angeles, hasTechnologyInFiction, voice-activated systems]
  • A. featuresFictionalTechnology chosen
    Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
  • B. hasFeatureInFiction
    Indicates that a fictional work includes or portrays a particular feature, trait, or characteristic.
  • C. inUniverseTechnologyOf
    Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
  • D. hasTechnologyTheme
    Indicates that something is associated with, centers on, or prominently features technology as a primary theme or subject.
  • E. inUniverseTechnologyDeveloped
    Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
  • 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_69d806a872d08190a329806f8ff30df4 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98154c9f48190aeca779d97151759 completed April 10, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69d98041a3548190a05ddd83dbb660fa completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:05 p.m.