Triple

T15445822
Position Surface form Disambiguated ID Type / Status
Subject Giulio Cesare E370019 entity
Predicate instanceOf P0 FINISHED
Object Conte di Cavour-class battleship C36169 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: Conte di Cavour-class battleship
Context triple: [Giulio Cesare, instanceOf, Conte di Cavour-class battleship]
  • 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. Kongō-class battleship
    The Kongō-class battleship was a group of fast capital ships of the Imperial Japanese Navy, originally built as battlecruisers in the early 20th century and later extensively modernized into fast battleships that served prominently in World War II.
  • C. Iron Duke-class battleship
    The Iron Duke-class battleship was a group of four British Royal Navy dreadnoughts built in the early 1910s, featuring ten 13.5-inch guns and improved armor and fire control, that served as the backbone of the Grand Fleet during World War I.
  • D. Nelson-class battleship
    The Nelson-class battleship was a British Royal Navy class of two treaty-era capital ships, HMS Nelson and HMS Rodney, distinguished by their forward-concentrated main armament and heavy armor designed under the constraints of the Washington Naval Treaty.
  • 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. 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
Created at: April 10, 2026, 3:21 a.m.