Triple
T1181294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guests of Honor |
E25142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction convention tradition |
C2656
|
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 convention tradition Context triple: [Guests of Honor, instanceOf, science fiction convention tradition]
-
A.
science fiction convention
chosen
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.
-
B.
fan convention
A fan convention is a large organized gathering where enthusiasts of specific media, genres, or hobbies come together to celebrate, meet creators and celebrities, attend panels and activities, and connect with fellow fans.
-
C.
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.
-
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 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.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.