Triple
T25982239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand sea lion/rāpoka Threat Management Plan |
E646100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | threat management plan |
C50407
|
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: threat management plan Context triple: [New Zealand sea lion/rāpoka Threat Management Plan, instanceOf, threat management plan]
-
A.
terrorism threat advisory system
A terrorism threat advisory system is a structured framework that continuously assesses, categorizes, and communicates the likelihood and severity of terrorist activities to guide security measures and public awareness.
-
B.
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.
-
C.
security strategy
A security strategy is a comprehensive, long-term plan that defines how an organization identifies, prioritizes, and mitigates risks to protect its assets, operations, and stakeholders.
-
D.
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.
-
E.
security management framework
A security management framework is a structured set of policies, processes, roles, and controls that organizations use to systematically identify, assess, manage, and monitor security risks to their information and assets.
- F. None of above. chosen
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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:54 a.m.