Triple

T31569632
Position Surface form Disambiguated ID Type / Status
Subject Small Changes E805520 entity
Predicate instanceOf P0 FINISHED
Object hard science fiction work C46212 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07 
Target class: hard science fiction work
Context triple: [Small Changes, instanceOf, hard science fiction work]
  • A. hard science fiction series
    A hard science fiction series is a collection of stories that emphasize scientific accuracy, rigorous technological detail, and plausible extrapolation of real-world science to explore speculative futures or phenomena.
  • B. science fantasy work
    A science fantasy work is a narrative that blends advanced scientific or technological elements with magical, mythical, or supernatural components in a single cohesive setting or storyline.
  • C. science-in-fiction novel chosen
    A science-in-fiction novel is a narrative that foregrounds real scientific concepts, methods, or communities as central drivers of plot and character, while remaining primarily a work of imaginative fiction rather than speculative science.
  • D. science fiction novel
    A science fiction novel is a long-form narrative that explores speculative futures, advanced technologies, or alternative realities to examine their impact on individuals, societies, and the nature of existence.
  • E. early science fiction work
    An early science fiction work is a narrative, typically from the 19th or early 20th century, that uses speculative scientific or technological ideas to explore imagined futures, alternate realities, or extraordinary phenomena before the genre’s conventions were firmly established.
  • F. None of above.

Provenance (1 batch)

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_69f348d2ee94819091918d1789398c29 completed April 30, 2026, 12:19 p.m.
Created at: April 30, 2026, 10:19 p.m.