Triple
T28843555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V-22 Osprey program |
E728388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense 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: defense procurement program Context triple: [V-22 Osprey program, instanceOf, defense 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.
defense acquisition program office
A defense acquisition program office is an organizational entity responsible for planning, managing, and overseeing the cost, schedule, performance, and risk of a specific military system or capability from development through sustainment.
-
C.
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.
-
D.
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.
-
E.
government procurement program
A government procurement program is a structured system through which public sector entities acquire goods, services, and works from external suppliers in accordance with defined policies, regulations, and budgetary 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:41 a.m.