Triple
T23111846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galactic Patrol |
E576340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | work in the Lensman series |
C41012
|
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: work in the Lensman series Context triple: [Galactic Patrol, instanceOf, work in the Lensman series]
-
A.
hard science fiction series
A hard science fiction series is a collection of stories that emphasize scientific accuracy, rigorous technological detail, and plausible extrapolation of real-world science to explore speculative futures or phenomena.
-
B.
science fantasy work
chosen
A science fantasy work is a narrative that blends advanced scientific or technological elements with magical, mythical, or supernatural components in a single cohesive setting or storyline.
-
C.
work on spaceflight
Work on spaceflight encompasses the research, engineering, operations, and support activities involved in designing, launching, operating, and sustaining vehicles and missions beyond Earth’s atmosphere.
-
D.
early science fiction work
An early science fiction work is a narrative, typically from the 19th or early 20th century, that uses speculative scientific or technological ideas to explore imagined futures, alternate realities, or extraordinary phenomena before the genre’s conventions were firmly established.
-
E.
spaceship in fiction
A spaceship in fiction is a technologically advanced vehicle designed for travel through outer space, often serving as a setting, plot device, or symbol of exploration and conflict in speculative narratives.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 3:58 p.m.