Triple
T31305781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project 949 |
E798332
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet submarine project |
C59122
|
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: Soviet submarine project Context triple: [Project 949, instanceOf, Soviet submarine project]
-
A.
Russian submarine class
chosen
A Russian submarine class is a category of submarines designed, built, and operated by Russia (or the former Soviet Union) that share common specifications, capabilities, and intended naval roles.
-
B.
Akula-class submarine
The Akula-class submarine is a series of nuclear-powered attack submarines developed by the Soviet Union and operated by Russia, designed for stealthy anti-ship and anti-submarine warfare in deep ocean environments.
-
C.
fictional ballistic missile submarine
A fictional ballistic missile submarine is an imagined, stealth-capable naval vessel designed to operate covertly underwater while carrying and potentially launching long-range nuclear or conventional ballistic missiles as part of a narrative or speculative setting.
-
D.
I-15-class submarine
The I-15-class submarine was a series of large, long-range Japanese Imperial Navy fleet submarines of World War II, designed for reconnaissance and offensive operations across the Pacific.
-
E.
Walrus-class submarine
The Walrus-class submarine is a Dutch diesel-electric attack submarine class designed for covert intelligence gathering, special operations support, and anti-surface/anti-submarine warfare in both littoral and open-ocean environments.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:14 p.m.