Triple
T29012989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isher Empire |
E737218
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | setting element in science fiction literature |
C15949
|
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: setting element in science fiction literature Context triple: [Isher Empire, instanceOf, setting element in science fiction literature]
-
A.
science-in-fiction novel
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.
-
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 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.
-
D.
science fiction concept
chosen
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.
-
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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:43 a.m.