Triple
T4327617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONTEST |
E96670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counter-terrorism strategy |
C15640
|
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: counter-terrorism strategy Context triple: [CONTEST, instanceOf, counter-terrorism strategy]
-
A.
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.
-
B.
counterterrorism expert
A counterterrorism expert is a specialist who analyzes, prevents, and responds to terrorist threats by integrating intelligence, security strategies, and policy guidance to protect people and critical infrastructure.
-
C.
counterterrorism database
A counterterrorism database is a centralized, secure repository that stores, organizes, and enables analysis of information related to terrorist organizations, individuals, activities, and incidents to support prevention, investigation, and response efforts.
-
D.
terrorist attack
A terrorist attack is a deliberate act of violence or threat of violence, typically against civilians or symbolic targets, carried out to instill fear and advance political, ideological, or religious objectives.
-
E.
terrorist
A terrorist is an individual who uses or threatens violence, often against civilians, to instill fear and achieve political, ideological, or religious objectives outside the bounds of lawful conflict.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:13 p.m.