Triple
T9959567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AJP-3.20 Allied Joint Doctrine for Cyberspace Operations |
E195531
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyberspace operations 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: cyberspace operations doctrine Context triple: [AJP-3.20 Allied Joint Doctrine for Cyberspace Operations, instanceOf, cyberspace operations doctrine]
-
A.
warfighting doctrine
Warfighting doctrine is a formalized body of principles and concepts that guides how a military plans, organizes, and conducts operations to achieve strategic and tactical objectives in conflict.
-
B.
security doctrine
chosen
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.
-
C.
space operations command
A space operations command is a military or governmental organizational unit responsible for planning, directing, and controlling space-based assets and activities to support national security, communications, navigation, and situational awareness.
-
D.
space operations
Space operations encompass the planning, execution, and management of activities involving spacecraft, satellites, and related systems to support missions such as communication, navigation, exploration, and defense in the space environment.
-
E.
maritime operations doctrine
Maritime operations doctrine is a comprehensive framework of principles, tactics, procedures, and guidelines that govern the planning, execution, and coordination of naval and maritime activities to achieve strategic, operational, and tactical objectives at sea.
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:46 p.m.