Triple
T25786154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block V |
E649422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Virginia-class submarine block |
C50990
|
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: Virginia-class submarine block Context triple: [Block V, instanceOf, Virginia-class submarine block]
-
A.
Vanguard-class submarine
The Vanguard-class submarine is a class of British nuclear-powered ballistic missile submarines designed to provide the United Kingdom’s continuous at-sea nuclear deterrent.
-
B.
James Madison-class submarine
The James Madison-class submarine was a series of U.S. Navy nuclear-powered ballistic missile submarines built in the 1960s as part of the Cold War strategic deterrent force, designed to carry Polaris and later Poseidon submarine-launched ballistic missiles.
-
C.
Victoria-class submarine
The Victoria-class submarine is a class of diesel-electric, conventionally powered attack submarines operated by the Royal Canadian Navy, designed for stealthy coastal defense, surveillance, and anti-submarine warfare.
-
D.
Columbia-class submarine
The Columbia-class submarine is a next-generation U.S. Navy nuclear-powered ballistic missile submarine designed to replace the Ohio-class as the cornerstone of America’s sea-based strategic nuclear deterrent.
-
E.
Ohio-class ballistic missile submarine
The Ohio-class ballistic missile submarine is a nuclear-powered U.S. Navy vessel designed for stealthy, long-duration patrols carrying submarine-launched ballistic missiles as a key component of the nation's strategic nuclear deterrent.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:55 a.m.