Triple
T33151762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Nürnberg |
E848456
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Königsberg-class light cruiser |
C58215
|
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: Königsberg-class light cruiser Context triple: [SMS Nürnberg, instanceOf, Königsberg-class 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.
Bremen-class cruiser
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.
-
C.
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.
-
D.
Zara-class heavy cruiser
The Zara-class heavy cruiser was a group of Italian Regia Marina warships of the interwar period, designed with heavy armor and 8-inch guns to maximize protection and firepower within Washington Naval Treaty limits.
-
E.
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.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:28 a.m.