Triple
T17216230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hitchhiker’s Guide to the Galaxy fandom |
E417859
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction fandom |
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: science fiction fandom Context triple: [The Hitchhiker’s Guide to the Galaxy fandom, instanceOf, science fiction fandom]
-
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 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 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 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.
-
E.
science fiction critic
A science fiction critic is a reviewer and analyst who evaluates and interprets science fiction works, examining their themes, literary quality, cultural impact, and relationship to the broader genre.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.