Triple
T20807119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise crew |
E512192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Starfleet crew |
C2469
|
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: Starfleet crew Context triple: [USS Enterprise crew, instanceOf, Starfleet crew]
-
A.
Star Trek character
chosen
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.
Star Trek species
A Star Trek species is a fictional sentient or non-sentient lifeform, often with distinct biological traits, cultures, and technologies, that inhabits the Star Trek universe and interacts with other species across space and time.
-
C.
Starfleet starship
A Starfleet starship is a versatile, warp-capable vessel operated by the United Federation of Planets for exploration, defense, diplomacy, and scientific research throughout space.
-
D.
UNSC military personnel
UNSC military personnel are the organized, trained, and equipped members of the United Nations Space Command’s armed forces responsible for conducting space, air, land, and naval operations to defend humanity and its interests.
-
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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:40 p.m.