Triple
T6140201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forrest J Ackerman |
E136941
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction historian |
C20002
|
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 historian Context triple: [Forrest J Ackerman, instanceOf, science fiction historian]
-
A.
science fiction writer
A science fiction writer is a creator of speculative narratives that explore imaginative futures, advanced technologies, alternative realities, or extraterrestrial life to examine the human condition and societal possibilities.
-
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 editor
A science fiction editor is a publishing professional who selects, refines, and shapes speculative narratives to ensure coherence, originality, and market appeal within the science fiction genre.
-
D.
science fiction hero
A science fiction hero is a courageous protagonist who confronts extraordinary futuristic or extraterrestrial challenges, often using advanced technology, intellect, or unique abilities to protect others and shape the fate of worlds.
-
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. 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.