Triple
T14239595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spearhead from Space |
E352971
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | science fiction television story |
C33637
|
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 television story Context triple: [Spearhead from Space, instanceOf, science fiction television story]
-
A.
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.
-
B.
science fiction screenplay
A science fiction screenplay is a written script that uses speculative science, futuristic settings, and imaginative technology to tell a cinematic story about characters confronting extraordinary circumstances beyond contemporary reality.
-
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 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.
-
E.
spy-fi television series
A spy-fi television series is a show that blends espionage and secret-agent tropes with science fiction elements such as advanced technology, futuristic settings, or speculative concepts.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:08 a.m.