Triple
T34984989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential Policy Directive 40 |
E1008920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | continuity policy directive |
C37842
|
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: continuity policy directive Context triple: [Presidential Policy Directive 40, instanceOf, continuity policy directive]
-
A.
continuity of government instrument
A continuity of government instrument is a tool, mechanism, or legal framework designed to ensure the uninterrupted functioning and authority of governmental operations during emergencies, crises, or disruptions.
-
B.
continuity of government framework
chosen
A continuity of government framework is a structured set of policies, plans, and procedures designed to ensure that essential governmental functions and leadership can continue or be rapidly restored during and after emergencies or disruptions.
-
C.
continuity feature
A continuity feature is a design element or mechanism that ensures a seamless, consistent experience or behavior across different states, times, or contexts within a system.
-
D.
business continuity management standard
A business continuity management standard is a formalized framework of policies, processes, and requirements that organizations use to identify potential disruptions and ensure the continued operation and rapid recovery of critical business functions.
-
E.
continuity tier
A continuity tier is a structured level or layer within a system that ensures consistent, uninterrupted operation or experience across changes, transitions, or time.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.