Triple
T3000766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry DeWolf-class offshore patrol vessel |
E81180
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arctic patrol ship class |
C12102
|
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: Arctic patrol ship class Context triple: [Harry DeWolf-class offshore patrol vessel, instanceOf, Arctic patrol ship class]
-
A.
Bagley-class destroyer
A Bagley-class destroyer is a type of U.S. Navy warship built in the late 1930s, characterized by high speed, heavy torpedo armament, and service in World War II as an escort and attack vessel.
-
B.
Gleaves-class destroyer
The Gleaves-class destroyer was a World War II-era United States Navy class of fast, versatile destroyers designed for anti-submarine warfare, convoy escort, and fleet screening operations.
-
C.
Benson-class destroyer
The Benson-class destroyer was a class of U.S. Navy warships built just before and during World War II, designed for high-speed escort, anti-submarine, and surface combat operations.
-
D.
I-class destroyer
An I-class destroyer is a fast, maneuverable warship designed primarily for fleet screening, anti-submarine warfare, and torpedo attacks, typically used by navies in the early to mid-20th century.
-
E.
Portland-class heavy cruiser
The Portland-class heavy cruiser was a class of U.S. Navy warships built in the early 1930s, designed under interwar treaty limitations to provide long-range, heavily armed surface combatants that balanced protection, speed, and firepower for fleet screening and offensive operations.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:59 p.m.