Triple
T10318305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Hood |
E242076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Admiral-class battlecruiser |
C6101
|
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: Admiral-class battlecruiser Context triple: [HMS Hood, instanceOf, Admiral-class battlecruiser]
-
A.
battlecruiser class
chosen
A battlecruiser class represents a large, fast, heavily armed warship optimized for long-range offensive power at the expense of some armor protection compared to battleships.
-
B.
Town-class light cruiser
The Town-class light cruiser was a series of British Royal Navy warships built in the 1930s and 1940s, designed for high-speed fleet screening, trade protection, and anti-aircraft defense with a balance of firepower and protection.
-
C.
Admiralen-class destroyer
The Admiralen-class destroyer was a series of Dutch naval destroyers built in the late 1920s and early 1930s for the Royal Netherlands Navy, designed for colonial service and fleet escort duties.
-
D.
Tribal-class destroyer
The Tribal-class destroyer was a class of large, fast, and heavily armed destroyers built for the Royal Navy and other Commonwealth navies in the late 1930s, designed to provide powerful fleet screening and offensive capabilities during World War II.
-
E.
Arethusa-class light cruiser
The Arethusa-class light cruiser was a group of small, fast Royal Navy warships built in the early 20th century, designed primarily for fleet scouting, destroyer flotilla leadership, and protection of larger capital 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:49 a.m.