Triple
T32374524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASy III |
E827240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | flight deck upgrade |
C53849
|
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: flight deck upgrade Context triple: [EASy III, instanceOf, flight deck upgrade]
-
A.
fighter aircraft upgrade configuration
A fighter aircraft upgrade configuration is a defined set of modifications, systems, and software enhancements applied to an existing fighter platform to improve its performance, capabilities, survivability, or mission adaptability.
-
B.
warship upgrade program
A warship upgrade program is a coordinated set of projects and processes aimed at modernizing naval vessels by enhancing their combat systems, sensors, propulsion, survivability, and support infrastructure to extend operational effectiveness and service life.
-
C.
naval engineering modification
chosen
A naval engineering modification is a targeted design or structural change made to a vessel or maritime system to improve its performance, safety, capability, or compliance with new operational requirements.
-
D.
shipboard seaplane
A shipboard seaplane is an aircraft designed to operate from water and be launched, recovered, and serviced from a ship, typically for reconnaissance, patrol, or liaison duties at sea.
-
E.
flying aircraft carrier
A flying aircraft carrier is a massive airborne platform that serves as a mobile base for launching, recovering, and supporting multiple aircraft while remaining aloft.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:50 a.m.