Triple
T6953702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trekkers |
E161189
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Star Trek fan |
C20001
|
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 fan Context triple: [Trekkers, instanceOf, Star Trek fan]
-
A.
science fiction fan
chosen
A science fiction fan is someone who enthusiastically engages with speculative stories about futuristic technology, space exploration, and imagined worlds, often participating in related communities and media.
-
B.
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.
-
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.
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.
-
E.
organization in the Star Trek universe
An organization in the Star Trek universe is a structured group of individuals, species, or entities with a defined purpose, hierarchy, and set of rules that operates within the political, social, or exploratory framework of the Star Trek setting.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:29 p.m.