Triple
T3038959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Advanced Strike Technology program |
E83078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military aviation technology 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 aviation technology program Context triple: [Joint Advanced Strike Technology program, instanceOf, military aviation technology program]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
military technology
Military technology encompasses the specialized tools, systems, and innovations developed and used by armed forces to enhance their capabilities in defense, offense, intelligence, and logistics.
-
E.
military project
A military project is a coordinated, goal-driven initiative undertaken by armed forces or defense organizations to develop, test, or deploy capabilities, technologies, or operations that enhance national security and military effectiveness.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:01 p.m.