Triple
T24529741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HNLMS Karel Doorman (joint support ship) |
E606769
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amphibious support ship |
C43006
|
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 support ship Context triple: [HNLMS Karel Doorman (joint support ship), instanceOf, amphibious support ship]
-
A.
amphibious assault ship class
An amphibious assault ship class is a group of large naval vessels designed to deploy, support, and command marine forces in amphibious operations using a combination of helicopters, landing craft, and sometimes short takeoff and vertical landing aircraft.
-
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.
amphibious warfare vessel class
chosen
An amphibious warfare vessel class is a group of naval ships designed and equipped to project ground forces from sea to shore, typically carrying troops, vehicles, and landing craft while providing command, control, and logistical support for amphibious operations.
-
D.
Iwo Jima-class amphibious assault ship
The Iwo Jima-class amphibious assault ship is a type of U.S. Navy vessel designed to embark, transport, and land Marine forces using helicopters and landing craft for amphibious operations.
-
E.
naval ship
A naval ship is a large, specially designed vessel operated by a nation's navy for military purposes such as defense, power projection, and maritime security.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
Created at: April 18, 2026, 2:25 a.m.