Triple
T17048037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 Birmingham abortion clinic bombing |
E413620
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-abortion violence incident |
C21512
|
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: anti-abortion violence incident Context triple: [1998 Birmingham abortion clinic bombing, instanceOf, anti-abortion violence incident]
-
A.
police brutality incident
A police brutality incident is an event in which law enforcement officers use excessive, unwarranted, or illegal force or misconduct against civilians, resulting in physical, psychological, or civil rights harm.
-
B.
anti-Black violence
Anti-Black violence is the systemic, institutional, and interpersonal use of physical, psychological, economic, or symbolic force that targets Black people and communities, rooted in anti-Black racism and histories of enslavement, colonialism, and racial hierarchy.
-
C.
anti-Armenian violence
Anti-Armenian violence refers to acts of physical, psychological, or structural harm, including discrimination, persecution, and mass atrocities, specifically targeting Armenians because of their ethnic or national identity.
-
D.
politically motivated violence
chosen
Politically motivated violence is the use or threat of physical force to influence, coerce, or change political decisions, institutions, or power structures.
-
E.
victim of police violence
A victim of police violence is an individual who has suffered physical, psychological, or civil rights harm as a result of excessive, unlawful, or discriminatory actions by law enforcement officers.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.