Triple
T20718905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Eridge |
E509254
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hunt-class escort destroyer |
C43496
|
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: Hunt-class escort destroyer Context triple: [HMS Eridge, instanceOf, Hunt-class escort destroyer]
-
A.
Edsall-class destroyer escort
The Edsall-class destroyer escort was a World War II-era class of U.S. Navy escort ships designed primarily for anti-submarine warfare and convoy protection in the Atlantic and Pacific theaters.
-
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.
Fletcher-class destroyer
A Fletcher-class destroyer is a fast, versatile World War II-era U.S. Navy warship designed for anti-air, anti-surface, and anti-submarine operations, notable for its robust armament, durability, and large production numbers.
-
D.
Charles F. Adams-class destroyer
The Charles F. Adams-class destroyer was a class of guided-missile destroyers built for the United States Navy during the Cold War, designed primarily for anti-air warfare and equipped with advanced radar and missile systems for fleet air defense.
-
E.
Cannon-class destroyer escort
The Cannon-class destroyer escort was a World War II-era U.S. Navy warship designed primarily for anti-submarine warfare and convoy escort duties, featuring diesel-electric propulsion and moderate armament for protection against submarines and aircraft.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:26 p.m.