Triple
T288516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Strategy of the United States |
E5938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national security strategy document |
C417
|
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: national security strategy document Context triple: [National Security Strategy of the United States, instanceOf, national security strategy document]
-
A.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
B.
founding document
A founding document is an authoritative text that formally establishes an organization, institution, or state by defining its core principles, structure, and governing rules.
-
C.
science policy document
A science policy document is a formal written record that outlines principles, guidelines, and strategic decisions governing the conduct, funding, regulation, and societal integration of scientific research and innovation.
-
D.
United States foreign policy doctrine
chosen
A United States foreign policy doctrine is a guiding framework of principles and strategic priorities that shapes how the U.S. engages with other nations and responds to international challenges.
-
E.
Cold War strategy
Cold War strategy is the overarching approach nations used to pursue geopolitical objectives through deterrence, proxy conflicts, ideological competition, and diplomatic maneuvering without escalating into direct large-scale war between nuclear-armed superpowers.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.