Triple
T13727981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warrior-class ironclad |
E329715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | armoured frigate class |
C34093
|
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: armoured frigate class Context triple: [Warrior-class ironclad, instanceOf, armoured frigate class]
-
A.
armoured cruiser
An armoured cruiser is a type of warship, prevalent in the late 19th and early 20th centuries, that combined heavy side armor and relatively high speed to serve in long-range scouting, commerce protection, and fleet support roles.
-
B.
Dido-class light cruiser
The Dido-class light cruiser was a class of British Royal Navy warships built before and during World War II, designed primarily as anti-aircraft cruisers with multiple dual-purpose guns to protect fleets from air and surface threats.
-
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.
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.
-
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. 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.