Triple
T31611803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akula I |
E806646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | submarine class variant |
C44855
|
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: submarine class variant Context triple: [Akula I, instanceOf, submarine class variant]
-
A.
submarine production variant
A submarine production variant is a specific, standardized version of a submarine design built in quantity, incorporating defined configurations, systems, and modifications distinct from other variants in the same class.
-
B.
T-class submarine
The T-class submarine is a British World War II-era diesel-electric attack submarine class designed for long-range patrols and operations in the Atlantic and Pacific Oceans.
-
C.
military submarine class
chosen
A military submarine class is a category of submarines sharing a common design, capabilities, and purpose, typically defined by their size, propulsion, armament, and intended operational roles.
-
D.
Virginia-class submarine variant
A Virginia-class submarine variant is a specific configuration or block of the U.S. Navy’s Virginia-class nuclear-powered attack submarines that incorporates distinct design changes, capability upgrades, or mission-specific enhancements compared to the baseline class.
-
E.
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.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:37 p.m.