Triple
T2374508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Lexington (CV-2) |
E46165
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Lexington-class aircraft carrier |
C5299
|
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: Lexington-class aircraft carrier Context triple: [USS Lexington (CV-2), instanceOf, Lexington-class aircraft carrier]
-
A.
Shōkaku-class aircraft carrier
The Shōkaku-class aircraft carrier was a pair of fast, large, and heavily armed Japanese fleet carriers of World War II, designed for high-capacity air operations and serving as key striking units of the Imperial Japanese Navy.
-
B.
aircraft carrier class
chosen
An aircraft carrier class is a conceptual category representing a group of aircraft carriers sharing a common design, capabilities, and intended operational role within a navy.
-
C.
Iowa-class battleship
The Iowa-class battleship is a fast, heavily armed and armored U.S. Navy capital ship designed in the World War II era to provide powerful naval gunfire support, fleet air defense, and high-speed escort capabilities.
-
D.
nuclear-powered aircraft carrier
A nuclear-powered aircraft carrier is a massive naval warship that uses nuclear reactors for propulsion and power, enabling it to launch, recover, and support aircraft operations over long durations without frequent refueling.
-
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.
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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
Created at: March 4, 2026, 7:56 p.m.