https://github.com/openeventdata/arabic_event_gsr
Gold standard records for Arabic event data
https://github.com/openeventdata/arabic_event_gsr
Last synced: 3 months ago
JSON representation
Gold standard records for Arabic event data
- Host: GitHub
- URL: https://github.com/openeventdata/arabic_event_gsr
- Owner: openeventdata
- License: mit
- Created: 2018-09-13T11:28:54.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2018-10-08T17:50:17.000Z (over 7 years ago)
- Last Synced: 2025-02-28T13:20:41.587Z (over 1 year ago)
- Size: 1.07 MB
- Stars: 2
- Watchers: 4
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# arabic_event_gsr
Gold standard records for Arabic event data
## Event Detection
We provide two "event detection" datasets for Arabic language event coding, one
for ASSAULT events and one for PROTEST events. These events are coded using the
[PLOVER](https://github.com/openeventdata/PLOVER) ontology, which is similar to
the [CAMEO](http://eventdata.parusanalytics.com/data.dir/cameo.html) ontology.
THese files can be used to test an automated coder's ability to recognize these
two event types in Arabic text.
`protest_gsr.csv` and `assault_gsr.csv` each have the following columns:
- `accept`: the number of annotators accepting the event label as true
- `event_type`: "ASSAULT" or "PROTEST", depending on the file
- `id`: the ID number of the sentence
- `label`: one of "yes", "easy no", "difficult no", or "ambiguous", depending
on the set of labels provided by annotators. "yes" is unanimous accept,
"easy no" is unanimous reject, "hard no" is mostly reject with a dissenting
accept, and "ambiguous" are entries with insufficent labels to be sure.
- `reject`: the number of annotators who rejected the label.
- `text`: the text shown to the annotator and that should be provided to the
event detection system
- `total`: the total number of annotations provided on the sentence.
## Span Recognition and Labeling
Another set of files (`assault_spans.json` and `protest_spans.json`) include
information for the gold standard recognized events, consisting of the event
verb, the source actor and target actor spans, and resulting CAMEO actor codes
for each.
`source_gold`, `target_gold`, and `verb_gold` report the common identified by
all coders as part of the span.
## Petrarch validation format
The two files are also available in XML format, suitable for use in
UniversalPetrarch.