Triple
T27503075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Excess Defense Articles program of the United States |
E694210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security assistance program |
C26610
|
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: security assistance program Context triple: [Excess Defense Articles program of the United States, instanceOf, security assistance program]
-
A.
security program
A security program is an organized set of policies, processes, technologies, and resources designed to protect an organization’s assets, information, and operations from threats and vulnerabilities.
-
B.
security application
A security application is a software system designed to protect digital assets by detecting, preventing, and responding to unauthorized access, malicious activities, and data breaches.
-
C.
security research advocacy program
A security research advocacy program is an organized initiative that promotes, supports, and coordinates ethical security research and responsible vulnerability disclosure between researchers, organizations, and the broader community.
-
D.
security initiative
A security initiative is a coordinated set of actions, policies, and resources designed to improve an organization’s protection against threats and vulnerabilities.
-
E.
security partnership
chosen
A security partnership is a collaborative relationship between organizations, agencies, or nations to share resources, information, and responsibilities for preventing, detecting, and responding to security threats.
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:12 p.m.