Triple
T21305500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS King George VI |
E525186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fictional ballistic missile submarine |
C44667
|
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: fictional ballistic missile submarine Context triple: [HMS King George VI, instanceOf, fictional ballistic missile submarine]
-
A.
nuclear-powered cruise missile submarine class
A nuclear-powered cruise missile submarine class is a group of submarines designed around a common blueprint that use nuclear reactors for propulsion and are primarily armed with long-range cruise missiles for land-attack or anti-ship missions.
-
B.
S-class submarine
The S-class submarine is a type of military undersea vessel, typically from the early to mid-20th century, designed for coastal patrol, reconnaissance, and torpedo attacks against enemy ships.
-
C.
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.
-
D.
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.
-
E.
military submarine
A military submarine is a stealth-capable naval vessel designed to operate underwater for extended periods to conduct surveillance, reconnaissance, and combat missions.
- 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 4:05 p.m.