Triple
T14639535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saru |
E343686
|
entity |
| Predicate | setting |
P1957
|
FINISHED |
| Object | Prime Timeline of Star Trek |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prime Timeline of Star Trek Context triple: [Saru, setting, Prime Timeline of Star Trek]
-
A.
Prime Timeline (Star Trek)
chosen
The Prime Timeline in Star Trek is the franchise’s main continuity in which the original television series and most subsequent series and films are set, distinct from alternate or rebooted timelines.
-
B.
Star Trek Kelvin timeline
The Star Trek Kelvin timeline is an alternate continuity within the Star Trek franchise, created by the events of the 2009 film reboot and featuring reimagined versions of the original series’ characters and stories.
-
C.
Star Trek: Prime Directive
Star Trek: Prime Directive is a science fiction novel set in the Star Trek universe that explores the ethical and dramatic consequences of Starfleet’s non-interference rule known as the Prime Directive.
-
D.
Star Trek: The Lost Era
Star Trek: The Lost Era is a series of Star Trek novels that explores the previously untold events and characters set between the eras of the original series films and Star Trek: The Next Generation.
-
E.
Star Trek: Corps of Engineers
Star Trek: Corps of Engineers is a Star Trek novel subseries that follows the adventures of the Starfleet engineering team aboard the USS da Vinci as they tackle complex technical crises and unusual space phenomena.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.