Triple
T11713591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland class |
E278435
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | class of heavy cruisers |
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: class of heavy cruisers Context triple: [Portland class, instanceOf, class of heavy cruisers]
-
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.
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.
Brooklyn-class light cruiser
The Brooklyn-class light cruiser was a class of fast, heavily armed U.S. Navy warships built in the 1930s, featuring fifteen 6-inch guns and designed to counter heavily gunned foreign cruisers while providing fleet screening and shore bombardment in World War II.
-
D.
cruiser class
A cruiser class is a category of medium-sized, fast, and heavily armed warships designed for long-range missions, independent operations, and fleet support.
-
E.
heavy cruiser
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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.