Triple
T9418344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscar-class submarine |
E227085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet submarine class |
C20948
|
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 class Context triple: [Oscar-class submarine, instanceOf, Soviet submarine class]
-
A.
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.
-
B.
Soviet Navy cruiser
A Soviet Navy cruiser is a large, fast, heavily armed warship designed by the Soviet Union for surface combat, air defense, and power projection at sea.
-
C.
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.
-
D.
Kirov-class light cruiser
The Kirov-class light cruiser was a series of Soviet warships built in the late 1930s, combining relatively heavy armament and high speed for fleet scouting, surface action, and support roles in World War II and the early Cold War.
-
E.
nuclear-powered fast attack submarine class
chosen
A nuclear-powered fast attack submarine class is a group of submarines designed for high-speed, long-endurance underwater operations focused on hunting enemy submarines and surface ships, intelligence gathering, and supporting naval strike missions.
- 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_69ca84359e7c819091148ba4b670e436 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:48 p.m.