Triple
T7194052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia-class submarine |
E167765
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nuclear-powered fast attack 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: nuclear-powered fast attack submarine class Context triple: [Virginia-class submarine, instanceOf, nuclear-powered fast attack submarine class]
-
A.
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.
-
B.
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.
-
C.
nuclear-powered aircraft carrier
A nuclear-powered aircraft carrier is a massive naval warship that uses nuclear reactors for propulsion and power, enabling it to launch, recover, and support aircraft operations over long durations without frequent refueling.
-
D.
Jaeger class
The Jaeger class is a category of large, agile, and heavily armed mechanized combat units designed for frontline engagement and rapid-response defense against massive threats.
-
E.
K-class destroyer
A K-class destroyer is a fast, maneuverable naval warship designed primarily for escort, patrol, and anti-submarine duties, typically armed with guns, torpedoes, and depth charges.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:50 p.m.