Triple
T2511273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direct Action Day |
E52703
|
entity |
| Predicate | violenceType |
P14172
|
FINISHED |
| Object | communal violence |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: communal violence | Statement: [Direct Action Day, violenceType, communal violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: violenceType Context triple: [Direct Action Day, violenceType, communal violence]
-
A.
hasTypeOfViolence
chosen
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
B.
involvesWeaponType
Indicates that the relationship or action includes the use, presence, or association of a specific type or category of weapon.
-
C.
typeOfAbuse
Indicates the specific kind or category of abusive behavior that one entity inflicts on another.
-
D.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
E.
viewOnViolence
Indicates an entity’s stance, opinion, or attitude toward the use of violence.
- F. None of above.
Provenance (3 batches)
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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.