Triple
T32979471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project 941 Akula |
E843756
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Typhoon-class submarine |
C59836
|
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: Typhoon-class submarine Context triple: [Project 941 Akula, instanceOf, Typhoon-class submarine]
-
A.
Balao-class submarine
The Balao-class submarine was a World War II-era U.S. Navy diesel-electric attack submarine class, an improved version of the Gato class, designed for long-range Pacific operations with enhanced diving depth and endurance.
-
B.
Astute-class submarine
The Astute-class submarine is a class of nuclear-powered fleet submarines built for the Royal Navy, designed for stealthy long-endurance operations including intelligence gathering, strike missions, and anti-submarine warfare.
-
C.
Valiant-class submarine
The Valiant-class submarine was a class of British nuclear-powered fleet submarines introduced in the 1960s, designed for fast, quiet operations and forming a key part of the Royal Navy’s Cold War undersea deterrent and attack capabilities.
-
D.
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.
-
E.
Archer-class submarine
The Archer-class submarine is a modern diesel-electric attack submarine class, based on the Swedish Västergötland design and upgraded for the Republic of Singapore Navy with advanced sensors, weapons, and air-independent propulsion for enhanced stealth and endurance.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.