Triple
T31014294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFP Procurement Service |
E790286
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military procurement unit |
C30532
|
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 procurement unit Context triple: [AFP Procurement Service, instanceOf, military procurement unit]
-
A.
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.
-
B.
military unit component
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
C.
organizational unit of the U.S. Department of Defense
An organizational unit of the U.S. Department of Defense is a formally established component—such as a department, command, agency, or office—responsible for specific defense-related functions, missions, and authorities within the overall DoD structure.
-
D.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
E.
procurement organisation
chosen
A procurement organisation is an entity responsible for strategically sourcing, negotiating, and managing the acquisition of goods and services to meet an organisation’s operational and financial 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.