Triple
T18099130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Beast (story) |
E433168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction horror short story |
C676
|
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: science fiction horror short story Context triple: [Star Beast (story), instanceOf, science fiction horror short story]
-
A.
science fiction novelette
A science fiction novelette is a mid-length speculative narrative, typically between a short story and a novella, that explores futuristic, technological, or otherworldly concepts with enough scope to develop complex ideas and characters.
-
B.
horror story
chosen
A horror story is a narrative designed to evoke fear, dread, or unease by confronting characters with terrifying, often supernatural or psychologically disturbing events.
-
C.
cosmic horror fiction
Cosmic horror fiction is a genre that explores humanity’s insignificance in a vast, indifferent universe by confronting characters with incomprehensible, often otherworldly forces that defy rational understanding.
-
D.
science fiction television story
A science fiction television story is a narrative episode or serial that uses speculative science, futuristic settings, or advanced technology to explore imaginative scenarios, often addressing social, philosophical, or ethical themes.
-
E.
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.
- 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_69d8b90916008190a1f110bd7ced5473 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:27 a.m.