Triple
T35474444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Future Lynx |
E1025291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | helicopter modernization program |
C40277
|
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: helicopter modernization program Context triple: [Future Lynx, instanceOf, helicopter modernization program]
-
A.
military aircraft conversion program
A military aircraft conversion program is an organized effort to modify existing aircraft—such as fighters, transports, or trainers—with new systems, structures, or roles to extend service life, enhance capabilities, or adapt them to evolving mission requirements.
-
B.
U.S. Army aviation program
The U.S. Army aviation program encompasses the development, training, operation, and maintenance of rotary- and fixed-wing aircraft to provide air mobility, reconnaissance, attack, and support capabilities for Army missions.
-
C.
rotorcraft development program
chosen
A rotorcraft development program is an organized, multi-phase effort to design, test, certify, and field new or improved rotary-wing aircraft to meet specified performance, safety, and mission requirements.
-
D.
military helicopter
A military helicopter is a rotary-wing aircraft designed and equipped for combat, transport, reconnaissance, and support missions in military operations.
-
E.
helicopter training platform
A helicopter training platform is a specialized system or environment that provides realistic, controlled conditions for pilots to learn, practice, and refine helicopter operation and emergency procedures.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.