Triple
T34976274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-B) |
E1008683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Constitution of the United Federation of Planets starship |
C17830
|
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: Constitution of the United Federation of Planets starship Context triple: [USS Enterprise (NCC-1701-B), instanceOf, Constitution of the United Federation of Planets starship]
-
A.
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.
-
B.
Constitution-class starship
chosen
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.
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.
-
D.
Romulan starship
A Romulan starship is a sleek, heavily armed and cloaked war vessel of the Romulan Star Empire, designed for stealth, intelligence gathering, and strategic strikes in interstellar conflicts.
-
E.
California-class starship
The California-class starship is a mid-sized Federation support vessel designed primarily for second-contact, logistical, and administrative missions rather than front-line exploration or combat.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.