Triple
T23047860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATA |
E573926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counterterrorism assistance program |
C27488
|
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: counterterrorism assistance program Context triple: [ATA, instanceOf, counterterrorism assistance program]
-
A.
counterterrorism initiative
chosen
A counterterrorism initiative is a coordinated set of policies, operations, and programs designed to prevent, detect, and respond to terrorist threats and activities.
-
B.
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.
-
C.
counter-terrorism organization
A counter-terrorism organization is an entity, typically governmental or intergovernmental, dedicated to preventing, detecting, and responding to terrorist activities through intelligence, law enforcement, military, and policy measures.
-
D.
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.
-
E.
counterterrorism law
Counterterrorism law is the body of domestic and international legal rules, procedures, and powers designed to prevent, investigate, and punish acts of terrorism while balancing national security with the protection of civil liberties and human rights.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:54 p.m.