Triple
T33106433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Dresden |
E847201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German light cruiser |
C39382
|
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: German light cruiser Context triple: [SMS Dresden, instanceOf, German light cruiser]
-
A.
Magdeburg-class light cruiser
The Magdeburg-class light cruiser was a group of early 20th-century German Imperial Navy warships designed for reconnaissance and fleet screening, featuring relatively light armor, high speed, and a main battery of 10.5 cm guns.
-
B.
Deutschland-class cruiser
The Deutschland-class cruiser was a group of German "pocket battleships" built in the interwar period, designed with heavy armament and long range to outgun cruisers and outrun battleships under the constraints of the Treaty of Versailles.
-
C.
Bremen-class cruiser
chosen
The Bremen-class cruiser was a group of early 20th-century German light cruisers built for the Imperial German Navy, designed for overseas service and fleet scouting with a balance of speed, armament, and protection.
-
D.
Derfflinger-class battlecruiser
The Derfflinger-class battlecruiser was a group of German Imperial Navy capital ships of World War I that combined heavy armament and relatively high speed with improved armor protection compared to earlier German battlecruisers.
-
E.
Königsberg-class light cruiser
The Königsberg-class light cruiser was a group of German interwar warships designed for high-speed scouting and commerce raiding, featuring relatively heavy armament and advanced engineering for their size within the constraints of the Treaty of Versailles.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.