Triple
T30728371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock In series |
E782344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | near-future science fiction |
C40750
|
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: near-future science fiction Context triple: [Lock In series, instanceOf, near-future science fiction]
-
A.
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.
-
B.
science fiction subgenre
chosen
A science fiction subgenre is a more narrowly defined category within science fiction that focuses on specific themes, settings, technologies, or narrative styles, such as cyberpunk, space opera, or hard science fiction.
-
C.
science fiction novelette
A science fiction novelette is a mid-length speculative narrative, typically between a short story and a novella, that explores futuristic, technological, or otherworldly concepts with enough scope to develop complex ideas and characters.
-
D.
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.
-
E.
science fiction movement
A science fiction movement is a collective trend or school within science fiction characterized by shared themes, aesthetics, and narrative approaches that respond to particular cultural, technological, or philosophical concerns.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:37 p.m.