Triple
T31081597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS King Alfred |
E792109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Drake-class armoured 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 armoured cruiser Context triple: [HMS King Alfred, instanceOf, Drake-class armoured 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.
Drake-class cruiser
chosen
The Drake-class cruiser is a versatile, medium-tonnage warship designed for extended independent operations, combining strong forward-facing firepower, durable shielding, and efficient propulsion for rapid response and 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.
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.
-
E.
Danae-class light cruiser
The Danae-class light cruiser was a group of British Royal Navy warships built during and shortly after World War I, designed for fleet scouting and trade protection with improved armament and speed over preceding light cruiser classes.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.