Triple
T15179512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian cruiser Bartolomeo Colleoni |
E362703
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian Navy 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: Italian Navy cruiser Context triple: [Italian cruiser Bartolomeo Colleoni, instanceOf, Italian Navy cruiser]
-
A.
Littorio-class battleship
The Littorio-class battleship was a group of fast, heavily armed and armored Italian capital ships of the Regia Marina built in the late 1930s, designed to counter French naval power and serve as the core of Italy’s battle fleet in World War II.
-
B.
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.
-
C.
armed merchant cruiser
An armed merchant cruiser is a civilian merchant ship that has been equipped with weapons and commissioned for naval service, typically for patrol, escort, or commerce raiding duties.
-
D.
Polish Navy ship
A Polish Navy ship is a naval vessel commissioned by Poland’s maritime armed forces, designed and equipped to perform military, patrol, support, and defense operations at sea under the Polish flag.
-
E.
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.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:09 a.m.