Triple
T2565246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Indianapolis (CA-35) |
E57335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portland-class heavy 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 heavy cruiser Context triple: [USS Indianapolis (CA-35), instanceOf, Portland-class heavy cruiser]
-
A.
Pennsylvania-class battleship
The Pennsylvania-class battleship was a pair of U.S. Navy super-dreadnoughts, led by USS Pennsylvania, designed in the 1910s with heavy armor and twelve 14-inch guns for fleet engagements and later modernized for extensive service in World War II.
-
B.
Benson-class destroyer
The Benson-class destroyer was a class of U.S. Navy warships built just before and during World War II, designed for high-speed escort, anti-submarine, and surface combat operations.
-
C.
I-class destroyer
An I-class destroyer is a fast, maneuverable warship designed primarily for fleet screening, anti-submarine warfare, and torpedo attacks, typically used by navies in the early to mid-20th century.
-
D.
Gleaves-class destroyer
The Gleaves-class destroyer was a World War II-era United States Navy class of fast, versatile destroyers designed for anti-submarine warfare, convoy escort, and fleet screening operations.
-
E.
Wyoming-class battleship
The Wyoming-class battleship was a pair of early 20th-century U.S. Navy dreadnoughts featuring twelve 12-inch guns, improved armor, and served primarily in World War I and interwar training roles.
- F. None of above. chosen
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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.