Triple

T33970888
Position Surface form Disambiguated ID Type / Status
Subject USS Portland (CA-33) E870986 entity
Predicate instanceOf P0 FINISHED
Object Portland-class cruiser C10535 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: Portland-class cruiser
Context triple: [USS Portland (CA-33), instanceOf, Portland-class cruiser]
  • A. Portland-class heavy cruiser chosen
    The Portland-class heavy cruiser was a class of U.S. Navy warships built in the early 1930s, designed under interwar treaty limitations to provide long-range, heavily armed surface combatants that balanced protection, speed, and firepower for fleet screening and offensive operations.
  • B. Belknap-class cruiser
    The Belknap-class cruiser was a class of U.S. Navy guided-missile cruisers (originally designated DLG frigates) designed in the 1960s for fleet air defense and anti-submarine warfare, featuring advanced radar and missile systems.
  • C. Baltimore-class heavy cruiser
    The Baltimore-class heavy cruiser was a class of fast, heavily armed U.S. Navy warships of World War II and the early Cold War, designed for long-range escort, surface action, and anti-aircraft defense.
  • D. York-class heavy cruiser
    The York-class heavy cruiser was a class of British Royal Navy warships built in the late 1920s, designed as smaller, treaty-compliant 8-inch gun cruisers for long-range patrol, trade protection, and fleet support duties.
  • E. Cleveland-class light cruiser
    The Cleveland-class light cruiser was a World War II-era U.S. Navy warship class designed as fast, heavily armed anti-aircraft and surface combatants, featuring twelve 6-inch guns and extensive secondary armament on a relatively compact, agile hull.
  • 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_69f3499ce8e88190b66e1d49ad8c7037 completed April 30, 2026, 12:22 p.m.
Created at: May 1, 2026, 1:50 a.m.