Triple
T20226488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double Helix: Double or Nothing |
E495395
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Trek novel |
C43159
|
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: Star Trek novel Context triple: [Double Helix: Double or Nothing, instanceOf, Star Trek novel]
-
A.
Star Wars novel
A Star Wars novel is a prose narrative set in the Star Wars universe that expands its characters, events, and lore beyond the films through original or adapted storytelling.
-
B.
Star Wars novel series
A Star Wars novel series is a collection of interconnected books set in the Star Wars universe that expand on its characters, events, and lore beyond the films.
-
C.
Star Trek continuity
Star Trek continuity is the cohesive, evolving narrative framework that connects the events, characters, timelines, and canon across all Star Trek series and films into a shared fictional universe.
-
D.
Star Trek television series
A Star Trek television series is a serialized science fiction show set in the Star Trek universe, following the missions and personal journeys of a starship crew or spacefaring organization as they explore new worlds, encounter alien species, and confront moral, political, and technological dilemmas.
-
E.
organization in Star Trek
An organization in Star Trek is a structured group of individuals, species, or entities—such as Starfleet, the Klingon High Council, or the Borg Collective—united by shared goals, rules, and hierarchies that shape political, military, scientific, or social dynamics within the Star Trek universe.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 11:39 p.m.