Triple
T768857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | War Plan Orange-3 |
E16235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States military plan |
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: United States military plan Context triple: [War Plan Orange-3, instanceOf, United States military plan]
-
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.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
C.
military operation
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
D.
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.
-
E.
NATO military position
A NATO military position is a standardized role or appointment within the North Atlantic Treaty Organization’s integrated command or force structure, defining specific responsibilities, rank equivalencies, and functions across member nations’ armed forces.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.