Triple
T11157296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leander class |
E263943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | class of light cruisers |
C11593
|
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 light cruisers Context triple: [Leander class, instanceOf, class of light cruisers]
-
A.
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.
-
B.
Town-class light cruiser
The Town-class light cruiser was a series of British Royal Navy warships built in the 1930s and 1940s, designed for high-speed fleet screening, trade protection, and anti-aircraft defense with a balance of firepower and protection.
-
C.
Leander-class light cruiser
chosen
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.
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.
Atlanta-class light cruiser
The Atlanta-class light cruiser was a U.S. Navy World War II warship class designed primarily as fast, heavily armed anti-aircraft escorts, featuring numerous dual-purpose 5-inch guns and high speed for fleet screening and carrier protection.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:28 p.m.