Triple
T5374137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendezvous with Rama |
E108919
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hard science fiction novel |
C916
|
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: hard science fiction novel Context triple: [Rendezvous with Rama, instanceOf, hard science fiction novel]
-
A.
science fiction novel
chosen
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.
-
B.
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.
-
C.
science fiction concept
A science fiction concept is a speculative idea or premise, often grounded in imagined advances in science or technology, that explores alternative realities, futures, or universes and their impact on individuals or societies.
-
D.
fictional interstellar war
A fictional interstellar war is a large-scale, imagined conflict between civilizations or factions across multiple star systems, often involving advanced technology, alien species, and complex political or ideological struggles.
-
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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 2:03 p.m.