Triple
T17471801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Agincourt |
E425432
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Astute-class nuclear-powered attack submarine |
C35022
|
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: Astute-class nuclear-powered attack submarine Context triple: [HMS Agincourt, instanceOf, Astute-class nuclear-powered attack submarine]
-
A.
Astute-class submarine
chosen
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.
-
B.
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.
-
C.
nuclear-powered fast attack submarine class
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.
-
D.
Los Angeles-class submarine
The Los Angeles-class submarine is a nuclear-powered fast attack submarine designed for anti-submarine warfare, intelligence gathering, and strike missions for the United States Navy.
-
E.
S-class submarine
The S-class submarine is a type of military undersea vessel, typically from the early to mid-20th century, designed for coastal patrol, reconnaissance, and torpedo attacks against enemy ships.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.