Triple
T32323496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Futurians |
E825839
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction writers' group |
C60130
|
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 writers' group Context triple: [Futurians, instanceOf, science fiction writers' group]
-
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 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 collaborator
A science fiction collaborator is a creative partner who co-develops speculative worlds, futuristic technologies, and narrative ideas, blending imagination and scientific plausibility to produce cohesive sci-fi works.
-
D.
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.
-
E.
science fiction website
A science fiction website is an online platform dedicated to exploring speculative futures, advanced technologies, and imaginative worlds through articles, stories, media, and community discussion.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:47 a.m.