Triple
T20387566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Timeline |
E497997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Trek timeline |
C17671
|
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 timeline Context triple: [Prime Timeline, instanceOf, Star Trek timeline]
-
A.
Star Trek continuity
chosen
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.
-
B.
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.
-
C.
Star Trek novel
A Star Trek novel is a written work of fiction set in the Star Trek universe, expanding on its characters, species, and themes through original or adapted stories.
-
D.
Star Trek location
A Star Trek location is any distinct place within the Star Trek universe—such as planets, starships, space stations, or regions of space—where narrative events, exploration, and interactions occur.
-
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.
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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.