Triple
T15308055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian cruiser Zara |
E365954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Zara-class cruiser |
C31901
|
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: Zara-class cruiser Context triple: [Italian cruiser Zara, instanceOf, Zara-class cruiser]
-
A.
Zara-class heavy cruiser
chosen
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.
-
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.
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.
-
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.
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.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:16 a.m.