Triple
T20989503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkeye 2000 |
E516980
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aircraft system upgrade |
C14168
|
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: military aircraft system upgrade Context triple: [Hawkeye 2000, instanceOf, military aircraft system 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.
combat aircraft mission system suite
chosen
A combat aircraft mission system suite is an integrated collection of avionics, sensors, communication, navigation, and weapon management subsystems that work together to plan, execute, and support military air missions.
-
C.
military aircraft
A military aircraft is a powered flying vehicle specifically designed, equipped, and operated by armed forces to conduct combat, support, reconnaissance, or training missions in defense and warfare operations.
-
D.
aircraft life extension program
An aircraft life extension program is a structured set of engineering, maintenance, and modification activities designed to safely extend an aircraft’s operational service life beyond its original design limits.
-
E.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 1:49 p.m.