Triple
T3606102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMAS Canberra |
E76374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | County-class heavy cruiser |
C4857
|
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: County-class heavy cruiser Context triple: [HMAS Canberra, instanceOf, County-class heavy cruiser]
-
A.
Portland-class heavy cruiser
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.
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.
-
C.
Leander-class light cruiser
The Leander-class light cruiser was a group of British Royal Navy warships built in the 1930s, designed as fast, versatile cruisers for trade protection, fleet screening, and colonial patrol duties.
-
D.
World War II cruiser
A World War II cruiser is a fast, medium-sized warship designed for long-range operations, providing fleet screening, surface combat, and shore bombardment using a mix of guns, torpedoes, and later radar-directed fire control.
-
E.
heavy cruiser
chosen
A heavy cruiser is a large, fast warship designed for long-range operations, typically armed with medium-caliber naval guns and substantial armor, serving as a versatile surface combatant in a fleet.
- 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_69ad85d93dcc819094fba90cf70f4996 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:22 p.m.