Triple

T20095789
Position Surface form Disambiguated ID Type / Status
Subject Pyotr Velikiy E496396 entity
Predicate instanceOf P0 FINISHED
Object Kirov-class battlecruiser C23389 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: Kirov-class battlecruiser
Context triple: [Pyotr Velikiy, instanceOf, Kirov-class battlecruiser]
  • A. Kirov-class light cruiser
    The Kirov-class light cruiser was a series of Soviet warships built in the late 1930s, combining relatively heavy armament and high speed for fleet scouting, surface action, and support roles in World War II and the early Cold War.
  • B. Soviet Navy cruiser chosen
    A Soviet Navy cruiser is a large, fast, heavily armed warship designed by the Soviet Union for surface combat, air defense, and power projection at sea.
  • C. Revenge-class battleship
    The Revenge-class battleship is a World War I–era British Royal Navy capital ship class designed for heavy gunnery, strong armor protection, and relatively modest speed, intended primarily for line-of-battle engagements and fleet support.
  • D. 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.
  • E. Kaiser-class battleship
    The Kaiser-class battleship was a group of German dreadnoughts built for the Imperial German Navy in the early 20th century, featuring heavy armor, powerful main batteries, and improved propulsion for use in high-seas fleet engagements.
  • 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_69da626eee3881909f3454986d4a6511 completed April 11, 2026, 3:02 p.m.
Created at: April 11, 2026, 11:25 p.m.