Triple
T7228649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canberra-class landing helicopter dock |
E154847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amphibious assault ship class |
C21521
|
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: amphibious assault ship class Context triple: [Canberra-class landing helicopter dock, instanceOf, amphibious assault ship class]
-
A.
surface combatant class
A surface combatant class is a category of naval warships designed and equipped to engage enemy forces on or near the sea surface using a combination of offensive and defensive weapon systems.
-
B.
naval auxiliary ship
A naval auxiliary ship is a non-combat vessel that supports naval operations by providing services such as supply, repair, transport, and logistical assistance to combat ships and shore facilities.
-
C.
seaplane carrier
A seaplane carrier is a naval vessel designed to transport, launch, recover, and support seaplanes for reconnaissance, patrol, and other maritime aviation operations.
-
D.
Pensacola-class cruiser
The Pensacola-class cruiser was a pair of early U.S. Navy "treaty cruisers" built in the late 1920s, characterized by heavy 8-inch guns, relatively light armor, and high speed, serving prominently in the Pacific during World War II.
-
E.
Bagley-class destroyer
A Bagley-class destroyer is a type of U.S. Navy warship built in the late 1930s, characterized by high speed, heavy torpedo armament, and service in World War II as an escort and attack vessel.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:54 p.m.