Triple
T3038609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ark Royal (seaplane carrier) |
E83071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | seaplane carrier |
C13118
|
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: seaplane carrier Context triple: [HMS Ark Royal (seaplane carrier), instanceOf, seaplane carrier]
-
A.
missile carrier
A missile carrier is a vehicle or platform designed to transport, launch, and sometimes guide missiles toward designated targets.
-
B.
aircraft carrier class
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.
light aircraft carrier
A light aircraft carrier is a smaller, more economical naval vessel designed to operate a limited air wing for roles such as fleet air defense, anti-submarine warfare, and power projection, typically with fewer aircraft and reduced capabilities compared to full-sized fleet carriers.
-
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.
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.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:01 p.m.