Triple
T4458109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCPS |
E97781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. federal cybersecurity program |
C420
|
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: U.S. federal cybersecurity program Context triple: [NCPS, instanceOf, U.S. federal cybersecurity program]
-
A.
United States government program
A United States government program is an organized set of activities, services, or regulations funded and administered by federal agencies to achieve specific public policy goals or address national needs.
-
B.
cybersecurity agency
A cybersecurity agency is an organization that protects digital systems, networks, and data from cyber threats through monitoring, prevention, incident response, and security consulting.
-
C.
CIA program
A CIA program is an organized, often covert initiative or operation designed and managed by the Central Intelligence Agency to achieve specific intelligence, security, or foreign policy objectives.
-
D.
component of the Cybersecurity and Infrastructure Security Agency
A component of the Cybersecurity and Infrastructure Security Agency is an organizational unit or program within CISA that carries out specific cybersecurity, infrastructure protection, emergency communications, or risk management functions in support of the agency’s mission.
-
E.
United States federal government program
chosen
A United States federal government program is an organized set of activities, services, or regulations funded and administered by federal agencies to implement national policies and address public needs.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:33 p.m.