Triple
T18424544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-X program |
E442102
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aircraft procurement program |
C5349
|
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 procurement program Context triple: [T-X program, instanceOf, military aircraft procurement program]
-
A.
military procurement programme
chosen
A military procurement programme is an organized, often long-term government initiative to identify, acquire, and manage the development, purchase, and deployment of equipment, systems, and services for the armed forces.
-
B.
military program
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
C.
military rearmament program
A military rearmament program is a coordinated, government-directed initiative to expand, modernize, or restore a nation’s armed forces and weaponry in response to strategic, political, or security objectives.
-
D.
maritime patrol aircraft program
A maritime patrol aircraft program is an organized effort to design, acquire, operate, and sustain aircraft and supporting systems dedicated to long-range surveillance, anti-submarine warfare, and protection of maritime domains.
-
E.
aerospace program
An aerospace program is an organized initiative or series of projects focused on the research, development, testing, and operation of aircraft, spacecraft, and related technologies to achieve specific scientific, commercial, or defense objectives.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.