Triple
T8998306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gruer |
E214974
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | character in science fiction literature |
C15067
|
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: character in science fiction literature Context triple: [Gruer, instanceOf, character in science fiction literature]
-
A.
character in a dystopian novel
A character in a dystopian novel is an individual whose actions, beliefs, and conflicts reveal and challenge the oppressive, dehumanizing structures of a bleak, often authoritarian future society.
-
B.
phrase from science fiction
A phrase from science fiction is a short, often evocative expression originating in speculative narratives that encapsulates futuristic concepts, technologies, or worlds beyond current reality.
-
C.
science fiction hero
chosen
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.
-
D.
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.
-
E.
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.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:05 p.m.