Triple
T8460989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Total Strategy security doctrine |
E200037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security doctrine |
C24419
|
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 doctrine Context triple: [Total Strategy security doctrine, instanceOf, security doctrine]
-
A.
national security policy
National security policy is a government’s overarching framework of principles, strategies, and actions designed to protect a nation’s sovereignty, citizens, and critical interests from internal and external threats.
-
B.
public policy doctrine
A public policy doctrine is a legal principle that allows courts or governments to limit, invalidate, or shape actions, contracts, or decisions that conflict with the broader interests, values, or welfare of society.
-
C.
national security system
A national security system is an integrated framework of institutions, policies, technologies, and processes designed to protect a nation’s sovereignty, citizens, critical infrastructure, and interests from internal and external threats.
-
D.
national security infrastructure
National security infrastructure is the integrated system of physical facilities, technologies, organizations, and legal frameworks designed to protect a nation’s sovereignty, critical assets, and population from internal and external threats.
-
E.
U.S. national security directive
A U.S. national security directive is a formal, often classified, presidential instruction that establishes policies, objectives, and courses of action related to the nation’s security and foreign affairs.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:10 p.m.