Triple
T7277694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Center for the Study of Science Fiction |
E163070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction studies organization |
C20668
|
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 studies organization Context triple: [Center for the Study of Science Fiction, instanceOf, science fiction studies organization]
-
A.
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.
-
B.
science fiction convention
A science fiction convention is a organized gathering of fans, creators, and industry professionals celebrating science fiction and related genres through panels, screenings, cosplay, merchandise, and community activities.
-
C.
science fiction fan
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.
-
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 publisher
A science fiction publisher is a company or imprint that acquires, edits, produces, markets, and distributes speculative fiction works focused on futuristic, technological, or imaginative themes.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:59 p.m.