Triple
T11096775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internal Security Fund |
E262397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security-related funding programme |
C2953
|
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-related funding programme Context triple: [Internal Security Fund, instanceOf, security-related funding programme]
-
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 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.
-
C.
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.
-
D.
multiannual funding programme
chosen
A multiannual funding programme is a structured financial initiative that allocates resources over several years to support specified objectives, projects, or policy priorities within a defined framework and timeline.
-
E.
national security law program
A national security law program is an academic or training course of study that focuses on the legal frameworks, institutions, and policies governing a nation’s defense, intelligence, and security operations.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.