Triple
T9145845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexis A. Gilliland |
E219451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American science fiction fan |
C20001
|
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: American science fiction fan Context triple: [Alexis A. Gilliland, instanceOf, American science fiction fan]
-
A.
science fiction fan
chosen
A science fiction fan is someone who enthusiastically engages with speculative stories about futuristic technology, space exploration, and imagined worlds, often participating in related communities and media.
-
B.
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.
-
C.
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.
-
D.
science fiction historian
A science fiction historian researches, analyzes, and documents the development, themes, cultural impact, and evolution of science fiction across various media and historical periods.
-
E.
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.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:19 p.m.