Triple
T1240115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Overseas Contingency Operations |
E26638
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military funding category |
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 funding category Context triple: [Overseas Contingency Operations, instanceOf, military funding category]
-
A.
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.
-
B.
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.
-
C.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
E.
naval arsenal
A naval arsenal is a specialized military facility where warships are built, repaired, equipped, and supplied with weapons, ammunition, and other naval stores.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.