Triple
T5143422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starfleet |
E116013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organization in the Star Trek universe |
C17674
|
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: organization in the Star Trek universe Context triple: [Starfleet, instanceOf, organization in the Star Trek universe]
-
A.
Star Trek character
A Star Trek character is an individual—human, alien, or artificial—who exists within the Star Trek universe and contributes to its stories through their role, relationships, and development across various series and films.
-
B.
Gallifreyan organization
A Gallifreyan organization is a structured collective of Time Lords and associated entities from the planet Gallifrey, formed to govern, regulate, or influence temporal affairs and societal functions within Time Lord civilization.
-
C.
in-universe object
An in-universe object is any tangible or intangible item that exists within a fictional world's reality and can be perceived, used, or referenced by characters in that setting.
-
D.
Object from Doctor Who
An Object from Doctor Who is any in-universe item, device, artifact, or construct—often with advanced, alien, or time-travel-related properties—that characters interact with to drive the plot or explore the show's science-fiction concepts.
-
E.
phrase from science fiction
A phrase from science fiction is a short, often evocative expression originating in speculative narratives that encapsulates futuristic concepts, technologies, or worlds beyond current reality.
- 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_69bd4446c0e08190a7c29dc74976bf03 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:43 p.m.