Triple
T35312871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-C) |
E1019823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ambassador-class starship |
C62191
|
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: Ambassador-class starship Context triple: [USS Enterprise (NCC-1701-C), instanceOf, Ambassador-class starship]
-
A.
Galaxy-class starship
A Galaxy-class starship is a large, multi-mission Federation vessel designed for deep-space exploration, scientific research, and tactical operations, featuring advanced technology, powerful defenses, and extensive crew accommodations.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.