Triple
T34831355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDAP |
E1004071
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense acquisition program category |
C31928
|
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 acquisition program category Context triple: [MDAP, instanceOf, defense acquisition program category]
-
A.
military program category
A military program category is a classification grouping related defense initiatives, projects, or activities based on their purpose, function, or capability area within an armed forces structure.
-
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.
United States defense acquisition category
chosen
A United States defense acquisition category is a classification that groups defense acquisition programs based on their cost, complexity, and oversight requirements to determine the level of review and management they receive.
-
D.
military procurement programme
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.
-
E.
defense acquisition enterprise
The defense acquisition enterprise is the integrated system of organizations, processes, policies, and stakeholders responsible for conceiving, developing, procuring, and sustaining military capabilities to meet national security needs.
- 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_69f76db7d1b4819093bd4912d80d845d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.