Triple

T32323213
Position Surface form Disambiguated ID Type / Status
Subject Cities in Flight E825831 entity
Predicate fictionalTechnologyInventor P632 FINISHED
Object spindizzy 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: spindizzy | Statement: [Cities in Flight, fictionalTechnologyInventor, spindizzy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalTechnologyInventor
Context triple: [Cities in Flight, fictionalTechnologyInventor, spindizzy]
  • A. fictionalInvention
    Indicates that one entity is an invention or creation that exists only within the fictional context of another entity (such as a story, universe, or work).
  • B. hasInventorRoleOf
    Indicates that an entity holds or fulfills the role of inventor with respect to another entity (such as an invention, patent, or creative work).
  • C. featuresFictionalTechnology
    Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
  • D. wasInventedBy chosen
    Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
  • E. notableInventor
    Indicates that the subject is a well-known or historically significant inventor of the object.
  • 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_69f34912d0c48190bba75770660320e9 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69fdb45537288190b6791078d4a6899f completed May 8, 2026, 10 a.m.
PD Predicate disambiguation batch_69fdb39ad96481908376d7def9fafc13 completed May 8, 2026, 9:57 a.m.
Created at: May 1, 2026, 12:47 a.m.