Datasets:
patriziobellan
commited on
Commit
•
9742bba
1
Parent(s):
5442891
Update README.md
Browse files
README.md
CHANGED
@@ -51,11 +51,11 @@ task_ids:
|
|
51 |
|
52 |
- **Homepage:** https://pdi.fbk.eu/pet-dataset/
|
53 |
- **Paper:** https://arxiv.org/abs/2203.04860
|
54 |
-
- **Point of Contact:** pbellan@fbk.eu
|
55 |
|
56 |
### Dataset Summary
|
57 |
|
58 |
-
Abstract. Although there is a long tradition of work in NLP on extracting entities and relations from text, to date there exists little work on the acquisition of business processes from unstructured data such as textual corpora of process descriptions. With this work we aim at filling this gap and establishing the first steps towards bridging data-driven information extraction methodologies from Natural Language Processing and the model-based formalization that is aimed from Business Process Management. For this, we develop the first corpus of business process descriptions annotated with activities,
|
59 |
|
60 |
### Supported Tasks and Leaderboards
|
61 |
|
@@ -67,36 +67,44 @@ English
|
|
67 |
|
68 |
## Dataset Structure
|
69 |
|
70 |
-
Test set to beanchmark
|
71 |
|
72 |
### Data Instances
|
73 |
|
74 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
75 |
|
76 |
### Data Fields
|
77 |
|
78 |
-
|
79 |
-
|
80 |
-
|
81 |
-
|
82 |
-
|
83 |
-
|
84 |
-
|
85 |
-
"
|
86 |
-
"
|
87 |
-
"
|
88 |
-
"
|
89 |
-
"
|
90 |
-
"
|
91 |
-
"
|
92 |
-
"
|
93 |
-
"
|
94 |
-
"
|
95 |
-
"
|
96 |
-
"
|
97 |
-
"
|
98 |
-
"
|
99 |
-
"I-AND Gateway",
|
100 |
|
101 |
### Data Splits
|
102 |
|
@@ -159,8 +167,11 @@ Expert Annotators
|
|
159 |
|
160 |
### Dataset Curators
|
161 |
|
162 |
-
Patrizio Bellan
|
163 |
-
|
|
|
|
|
|
|
164 |
|
165 |
### Licensing Information
|
166 |
|
|
|
51 |
|
52 |
- **Homepage:** https://pdi.fbk.eu/pet-dataset/
|
53 |
- **Paper:** https://arxiv.org/abs/2203.04860
|
54 |
+
- **Point of Contact:** [Patrizio Bellan] (pbellan@fbk.eu)
|
55 |
|
56 |
### Dataset Summary
|
57 |
|
58 |
+
Abstract. Although there is a long tradition of work in NLP on extracting entities and relations from text, to date there exists little work on the acquisition of business processes from unstructured data such as textual corpora of process descriptions. With this work we aim at filling this gap and establishing the first steps towards bridging data-driven information extraction methodologies from Natural Language Processing and the model-based formalization that is aimed from Business Process Management. For this, we develop the first corpus of business process descriptions annotated with activities, actors, activity data, gateways and their conditions. We present our new resource to benchmark the difficulty and challenges of business process extraction from text.
|
59 |
|
60 |
### Supported Tasks and Leaderboards
|
61 |
|
|
|
67 |
|
68 |
## Dataset Structure
|
69 |
|
70 |
+
Test set to beanchmark *Business Process Extraction from Text* approaches.
|
71 |
|
72 |
### Data Instances
|
73 |
|
74 |
+
For each instance, there is a document name representing the name of the document of the Friedrich *et al.* dataset, an integer representing the number of the sentence, a list of tokens representing the words of the sentence instance, and a list of *ner tags* (in IOB2 format) representing the annotation of process elements of the sentence.
|
75 |
+
|
76 |
+
```
|
77 |
+
{
|
78 |
+
"document name":"doc-1.1",
|
79 |
+
"sentence-ID":1,
|
80 |
+
"tokens":["Whenever","the","sales","department","receives","an","order",",","a","new","process","instance","is","created","."],
|
81 |
+
"ner-tags":["O","B-Actor","I-Actor","I-Actor","B-Activity","B-Activity Data","I-Activity Data","O","O","O","O","O","O","O","O"]
|
82 |
+
}
|
83 |
+
```
|
84 |
|
85 |
### Data Fields
|
86 |
|
87 |
+
- *document name*: a string used to represent the name of the document.
|
88 |
+
- *sentence-ID*: an integer (starting from 0) representing the number of the sentence within the document.
|
89 |
+
- *tokens*: a list of string representing the words of the sentence
|
90 |
+
- *ner-tags*: a list of string representing the annotation for each word.
|
91 |
+
|
92 |
+
The allowed **ner-tags** are:
|
93 |
+
- "O":
|
94 |
+
- "B-Actor",
|
95 |
+
- "I-Actor",
|
96 |
+
- "B-Activity",
|
97 |
+
- "I-Activity",
|
98 |
+
- "B-Activity Data",
|
99 |
+
- "I-Activity Data",
|
100 |
+
- "B-Further Specification",
|
101 |
+
- "I-Further Specification",
|
102 |
+
- "B-XOR Gateway",
|
103 |
+
- "I-XOR Gateway",
|
104 |
+
- "B-Condition Specification",
|
105 |
+
- "I-Condition Specification",
|
106 |
+
- "B-AND Gateway",
|
107 |
+
- "I-AND Gateway",
|
|
|
108 |
|
109 |
### Data Splits
|
110 |
|
|
|
167 |
|
168 |
### Dataset Curators
|
169 |
|
170 |
+
- Patrizio Bellan (
|
171 |
+
- Mauro Dragoni
|
172 |
+
- Chiara Ghidini
|
173 |
+
- Han van der Aa
|
174 |
+
- Simone Ponzetto
|
175 |
|
176 |
### Licensing Information
|
177 |
|