Triple
T18487859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | postcyberpunk |
E451736
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction subgenre |
C40750
|
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 subgenre Context triple: [postcyberpunk, instanceOf, science fiction subgenre]
-
A.
comedic science fiction subgenre
A comedic science fiction subgenre blends futuristic or speculative science-based settings and concepts with humor, satire, and absurdity to playfully explore technology, space, and the human condition.
-
B.
science fiction movement
A science fiction movement is a collective trend or school within science fiction characterized by shared themes, aesthetics, and narrative approaches that respond to particular cultural, technological, or philosophical concerns.
-
C.
science fiction concept
A science fiction concept is a speculative idea or premise, often grounded in imagined advances in science or technology, that explores alternative realities, futures, or universes and their impact on individuals or societies.
-
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.
science fiction film
A science fiction film is a motion picture that explores speculative concepts such as advanced technology, space travel, time manipulation, or extraterrestrial life, often examining their impact on individuals and societies.
- F. None of above. chosen
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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:35 a.m.