Triple
T21708476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Defense Cooperation |
E535832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military assistance office |
C6686
|
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 assistance office Context triple: [Office of Defense Cooperation, instanceOf, military assistance office]
-
A.
military assistance program
A military assistance program is an organized initiative through which one nation or entity provides training, equipment, funding, or advisory support to strengthen the defense capabilities of another.
-
B.
military support organization
A military support organization is an entity that provides logistical, administrative, technical, and welfare services to enable and sustain the effective operation of armed forces.
-
C.
bureau of USAID
The bureau of USAID is a major organizational unit within the U.S. Agency for International Development responsible for planning, managing, and overseeing foreign assistance programs in a specific sector or geographic region.
-
D.
diplomatic mission unit
chosen
A diplomatic mission unit is an organizational subdivision within a diplomatic mission responsible for carrying out specific functions such as political, economic, consular, cultural, or administrative activities in support of a state's foreign relations.
-
E.
acquisition support organization
An acquisition support organization is a specialized entity that provides expertise, resources, and services to plan, manage, and execute procurement and acquisition activities efficiently and in compliance with relevant policies and regulations.
- 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_69e0c46b44c0819088ab883ebd44e0e8 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:46 p.m.