Triple
T12256737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multinational Joint Task Force |
E292122
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counterinsurgency task force |
C31169
|
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 task force Context triple: [Multinational Joint Task Force, instanceOf, counterinsurgency task force]
-
A.
counterterrorism task force
A counterterrorism task force is a specialized, multi-agency group organized to prevent, detect, and respond to terrorist threats and activities through intelligence gathering, operational coordination, and targeted interventions.
-
B.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
C.
occupation force
An occupation force is a military presence deployed by a controlling power to maintain authority, security, and administration over a captured or foreign territory.
-
D.
irregular military forces
Irregular military forces are non-state or semi-organized armed groups that operate outside formal national military structures, often using unconventional tactics and lacking official recognition as regular armed forces.
-
E.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
- F. None of above. chosen
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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.