Triple
T20716029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty (Klingon Bird-of-Prey) |
E509171
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Klingon Bird-of-Prey |
C43495
|
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: Klingon Bird-of-Prey Context triple: [HMS Bounty (Klingon Bird-of-Prey), instanceOf, Klingon Bird-of-Prey]
-
A.
Excelsior-class starship
The Excelsior-class starship is a large, advanced Federation starship designed for long-range exploration, tactical versatility, and high-warp performance in deep-space operations.
-
B.
Intrepid-class starship
The Intrepid-class starship is a versatile, mid-sized Federation vessel designed for deep-space exploration, scientific research, and rapid-response missions, balancing advanced technology with high speed and maneuverability.
-
C.
Sovereign-class starship
A Sovereign-class starship is a highly advanced, large Federation capital vessel designed for deep-space exploration, tactical superiority, and diplomatic missions, exemplified by the USS Enterprise-E.
-
D.
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.
-
E.
Corellian YT-1300 light freighter
A Corellian YT-1300 light freighter is a highly customizable, durable, and fast starship primarily used for cargo transport but often modified for smuggling, combat, and independent operations across the galaxy.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:15 p.m.