Triple
T38218205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three Warfares doctrine |
E1010741
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information warfare strategy |
C4796
|
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: information warfare strategy Context triple: [Three Warfares doctrine, instanceOf, information warfare strategy]
-
A.
information warfare organization
An information warfare organization is an entity structured to plan, conduct, and coordinate operations that manipulate, protect, or exploit information and information systems to achieve strategic, operational, or tactical objectives.
-
B.
military strategy
chosen
Military strategy is the high-level planning and directing of armed forces and resources to achieve political and military objectives in war or conflict.
-
C.
security strategy
A security strategy is a comprehensive, long-term plan that defines how an organization identifies, prioritizes, and mitigates risks to protect its assets, operations, and stakeholders.
-
D.
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.
-
E.
national cyber security strategy
A national cyber security strategy is a high-level, government-led framework that defines a country’s objectives, priorities, and coordinated actions to protect its digital infrastructure, data, and citizens from cyber threats while supporting economic and social development.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.