Triple
T19339099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Briggs Plan |
E483702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counterinsurgency 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: counterinsurgency strategy Context triple: [Briggs Plan, instanceOf, counterinsurgency strategy]
-
A.
counterinsurgency task force
A counterinsurgency task force is a coordinated, multi-agency military and civilian unit organized to detect, disrupt, and defeat insurgent groups while stabilizing and securing affected populations and territories.
-
B.
counter-terrorism strategy
A counter-terrorism strategy is a coordinated set of policies, operations, and preventive measures designed to detect, deter, disrupt, and respond to terrorist threats while balancing security needs with legal and ethical constraints.
-
C.
guerrilla conflict
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
D.
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.
-
E.
covert military conflict
A covert military conflict is a hidden or plausibly deniable struggle between states or organized groups that uses clandestine operations, proxies, and intelligence activities instead of overt, declared warfare.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.