Triple
T25822362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severe Threat Level |
E650436
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | terrorism alert level |
C21530
|
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: terrorism alert level Context triple: [Severe Threat Level, instanceOf, terrorism alert level]
-
A.
terrorism threat level
chosen
The terrorism threat level is a classification that indicates the assessed likelihood and immediacy of terrorist activities, guiding security measures and public awareness.
-
B.
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.
-
C.
international police alert
An international police alert is a formal notification issued by law enforcement agencies across national borders to share critical information about suspects, crimes, or security threats and to request cooperation from foreign authorities.
-
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.
emergency alerting standard
An emergency alerting standard is a formal specification that defines how urgent public safety messages are created, formatted, transmitted, and delivered across communication systems to warn and inform people during crises.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 7:30 a.m.