Triple
T32665907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Future Years Defense Program |
E835154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defense planning document |
C3532
|
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: defense planning document Context triple: [Future Years Defense Program, instanceOf, defense planning document]
-
A.
military planning document
chosen
A military planning document is a formal written plan that outlines objectives, strategies, resources, timelines, and contingencies for conducting military operations or activities.
-
B.
strategic document
A strategic document is a formal written plan that outlines an organization’s long-term goals, priorities, and actions for achieving its mission and competitive advantage.
-
C.
politico-military planning process
The politico-military planning process is a coordinated, iterative decision-making framework that integrates political objectives and military capabilities to develop, assess, and select feasible strategies and courses of action for achieving national or alliance security goals.
-
D.
government strategy document
A government strategy document is an official, forward-looking plan that outlines a public authority’s long-term goals, priorities, and coordinated actions for addressing specific policy areas or national challenges.
-
E.
security doctrine
A security doctrine is a formalized set of principles and strategies that guides how a state or organization understands, prioritizes, and responds to threats to its security.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:08 a.m.