Triple
T31007790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Good Hope |
E790117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Drake-class cruiser |
C57464
|
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: Drake-class cruiser Context triple: [HMS Good Hope, instanceOf, Drake-class cruiser]
-
A.
Leander-class cruiser
The Leander-class cruiser was a group of British light cruisers built in the 1930s, designed for trade protection and fleet duties, and widely employed by the Royal Navy and Commonwealth navies during World War II.
-
B.
Leander-class light cruiser
The Leander-class light cruiser was a group of British Royal Navy warships built in the 1930s, designed as fast, versatile cruisers for trade protection, fleet screening, and colonial patrol duties.
-
C.
Belknap-class cruiser
The Belknap-class cruiser was a class of U.S. Navy guided-missile cruisers (originally designated DLG frigates) designed in the 1960s for fleet air defense and anti-submarine warfare, featuring advanced radar and missile systems.
-
D.
Atlanta-class light cruiser
The Atlanta-class light cruiser was a U.S. Navy World War II warship class designed primarily as fast, heavily armed anti-aircraft escorts, featuring numerous dual-purpose 5-inch guns and high speed for fleet screening and carrier protection.
-
E.
Cleveland-class light cruiser
The Cleveland-class light cruiser was a World War II-era U.S. Navy warship class designed as fast, heavily armed anti-aircraft and surface combatants, featuring twelve 6-inch guns and extensive secondary armament on a relatively compact, agile hull.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.