Triple
T20391825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime Directive |
E498103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Starfleet regulation |
C43993
|
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 regulation Context triple: [Prime Directive, instanceOf, Starfleet regulation]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
Constitution-class starship
A Constitution-class starship is a Federation heavy cruiser designed for deep-space exploration, scientific research, and tactical engagements, exemplified by vessels like the USS Enterprise in the Star Trek universe.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:28 a.m.