Triple

T10522678
Position Surface form Disambiguated ID Type / Status
Subject Zhenyuan E248214 entity
Predicate instanceOf P0 FINISHED
Object ironclad battleship C11729 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: ironclad battleship
Context triple: [Zhenyuan, instanceOf, ironclad battleship]
  • A. 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.
  • 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. pre-dreadnought battleship chosen
    A pre-dreadnought battleship is a late-19th to early-20th-century capital warship characterized by a mixed-caliber armament, heavy armor, and relatively low speed, preceding the revolutionary all-big-gun dreadnought design.
  • D. 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.
  • 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_69d381c5c7448190bec34bee7ec72bac completed April 6, 2026, 9:49 a.m.
Created at: April 6, 2026, 12:29 p.m.