Triple
T10319906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIDE |
E242111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | terrorist database |
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 database Context triple: [TIDE, instanceOf, terrorist database]
-
A.
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.
-
B.
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.
-
C.
terrorist leader
A terrorist leader is an individual who plans, directs, and coordinates acts of terrorism, providing strategic guidance, resources, and ideological motivation to an organized group engaged in violent extremist activities.
-
D.
domestic terrorist
A domestic terrorist is an individual or group that commits or plans violent, criminal acts within their own country, motivated by ideological, political, religious, or social objectives intended to intimidate or coerce a population or government.
-
E.
terrorist attack target
A terrorist attack target is any person, place, system, or symbolic asset deliberately selected by terrorists to inflict harm, create fear, or achieve political, ideological, or religious objectives.
- 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.