Triple
T10319953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrorist Screening Database |
E242112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | terrorist watchlist |
C7893
|
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: terrorist watchlist Context triple: [Terrorist Screening Database, instanceOf, terrorist watchlist]
-
A.
terrorist watchlisting system
A terrorist watchlisting system is a centralized platform that collects, analyzes, and shares information on individuals suspected of terrorism-related activities to support threat detection, risk assessment, and operational decision-making by authorized agencies.
-
B.
counterterrorism database
chosen
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.
-
C.
most wanted list
A most wanted list is an official compilation of individuals sought by authorities, typically for serious crimes, prioritized for capture or information leading to their arrest.
-
D.
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.
-
E.
terrorism threat advisory system
A terrorism threat advisory system is a structured framework that continuously assesses, categorizes, and communicates the likelihood and severity of terrorist activities to guide security measures and public awareness.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:50 a.m.