Update README.md
Browse files
README.md
CHANGED
@@ -55,7 +55,9 @@ configs:
|
|
55 |
path: data/train-*
|
56 |
---
|
57 |
|
58 |
-
# Material Contracts (Exhibit 10) from SEC/EDGAR
|
|
|
|
|
59 |
|
60 |
## Table of Contents
|
61 |
- [Dataset Card Creation Guide](#dataset-card-creation-guide)
|
@@ -87,112 +89,134 @@ configs:
|
|
87 |
- [Citation Information](#citation-information)
|
88 |
- [Contributions](#contributions)
|
89 |
|
90 |
-
## Dataset Description
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
91 |
|
92 |
-
|
93 |
-
- **Repository:** [Crawler](https://github.com/ChenghaoMou/edgar-crawler/tree/main)
|
94 |
-
- **Paper:** NA
|
95 |
-
- **Leaderboard:** NA
|
96 |
-
- **Point of Contact:** mouchenghao at gmail dot com
|
97 |
|
98 |
-
|
99 |
|
100 |
-
|
101 |
|
102 |
-
### Supported Tasks and Leaderboards
|
103 |
|
104 |
-
-
|
105 |
|
106 |
-
Currently, there
|
107 |
|
108 |
-
### Languages
|
109 |
|
110 |
-
|
111 |
|
112 |
-
## Dataset Structure
|
113 |
|
114 |
-
### Data Instances
|
115 |
|
116 |
-
|
117 |
|
118 |
-
### Data Fields
|
|
|
|
|
119 |
|
120 |
| Field | Description |
|
121 |
|---|---|
|
122 |
-
| `index_html_url` |
|
123 |
-
| `index_text_url` |
|
124 |
-
| `cik` | Central Index Key from EDGAR |
|
125 |
-
| `name` | Company name |
|
126 |
-
| `type` |
|
127 |
-
| `date` |
|
128 |
-
| `seq` |
|
129 |
-
| `desc` |
|
130 |
-
| `doc_type` |
|
131 |
-
| `size` |
|
132 |
-
| `filename` |
|
133 |
-
| `file_url` |
|
134 |
-
| `file` | GCS file
|
135 |
-
| `__index_level_0__` |
|
136 |
-
| `file_content` |
|
|
|
|
|
|
|
|
|
137 |
|
138 |
-
|
139 |
|
140 |
-
|
141 |
|
142 |
-
|
143 |
|
144 |
-
###
|
145 |
|
|
|
146 |
|
147 |
-
|
148 |
|
|
|
149 |
|
150 |
-
|
151 |
|
152 |
-
|
153 |
|
154 |
-
|
155 |
|
|
|
156 |
|
157 |
-
|
158 |
|
|
|
159 |
|
160 |
-
|
161 |
|
162 |
-
|
|
|
|
|
163 |
|
164 |
### Personal and Sensitive Information
|
165 |
|
166 |
-
|
|
|
|
|
|
|
|
|
167 |
|
168 |
-
|
169 |
|
170 |
-
###
|
171 |
|
172 |
-
|
173 |
|
174 |
-
###
|
175 |
|
176 |
-
|
177 |
|
178 |
-
|
179 |
|
180 |
-
|
181 |
|
182 |
-
|
183 |
|
184 |
-
###
|
185 |
|
186 |
-
|
187 |
|
188 |
-
###
|
189 |
|
190 |
-
|
191 |
|
192 |
-
###
|
193 |
|
194 |
-
|
|
|
|
|
195 |
|
196 |
-
|
197 |
|
198 |
-
|
|
|
55 |
path: data/train-*
|
56 |
---
|
57 |
|
58 |
+
# <span style="color: #2c2c2c">Material Contracts (Exhibit 10) from SEC/EDGAR</span>
|
59 |
+
|
60 |
+
*<span style="color: #81b29a">Because sometimes you need 930,120 examples of corporate legalese to train your next model</span>* ☕
|
61 |
|
62 |
## Table of Contents
|
63 |
- [Dataset Card Creation Guide](#dataset-card-creation-guide)
|
|
|
89 |
- [Citation Information](#citation-information)
|
90 |
- [Contributions](#contributions)
|
91 |
|
92 |
+
## <span style="color: #e07a5f">Dataset Description</span>
|
93 |
+
|
94 |
+
Ever wondered what happens when you spend countless late nights crawling through SEC filings? You get this <span style="color: #81b29a">**beautifully curated collection**</span> of corporate contracts that'll make your legal AI models significantly smarter (and probably more verbose).
|
95 |
+
|
96 |
+
- **<span style="color: #e07a5f">Homepage:</span>** NA *<span style="color: #81b29a">(because who needs sleep when you have datasets?)</span>*
|
97 |
+
- **<span style="color: #e07a5f">Repository:</span>** [Crawler](https://github.com/ChenghaoMou/edgar-crawler/tree/main) *<span style="color: #81b29a">(the code that made this madness possible)</span>*
|
98 |
+
- **<span style="color: #e07a5f">Paper:</span>** NA *<span style="color: #81b29a">(too busy debugging to write papers)</span>*
|
99 |
+
- **<span style="color: #e07a5f">Leaderboard:</span>** NA *<span style="color: #81b29a">(but feel free to create one!)</span>*
|
100 |
+
- **<span style="color: #e07a5f">Point of Contact:</span>** mouchenghao at gmail dot com *<span style="color: #81b29a">(caffeine-powered responses guaranteed)</span>*
|
101 |
|
102 |
+
### <span style="color: #e07a5f">Dataset Summary</span>
|
|
|
|
|
|
|
|
|
103 |
|
104 |
+
Picture this: <span style="color: #e07a5f">**930,120 material contracts**</span> (Exhibit 10) painstakingly collected from sec.gov's EDGAR database. We're talking about legal agreements spanning from <span style="color: #81b29a">**1994 to January 2024**</span>, sourced from 10-K, 10-Q, and 8-K filings. Think of Exhibit 10 as the treasure trove where companies hide their most important legal paperwork – employment agreements, merger documents, licensing deals, and all those contracts that make corporate lawyers reach for their third espresso.
|
105 |
|
106 |
+
This isn't just another dataset – it's <span style="color: #81b29a">**three decades of corporate America's legal DNA**</span>, ready for your next language model to digest.
|
107 |
|
108 |
+
### <span style="color: #e07a5f">Supported Tasks and Leaderboards</span>
|
109 |
|
110 |
+
- <span style="color: #2c2c2c; background-color: #f4f3ee; padding: 2px 4px; border-radius: 3px;">`language-modeling`</span> or <span style="color: #2c2c2c; background-color: #f4f3ee; padding: 2px 4px; border-radius: 3px;">`text-generation`</span>: Perfect for building domain-specific models that understand the intricate dance of legal and financial language. Your model will learn to speak fluent "corporate" – complete with all those delightful <span style="color: #81b29a">*whereases*</span> and <span style="color: #81b29a">*heretofores*</span>.
|
111 |
|
112 |
+
Currently, there's no leaderboard for this dataset, but hey, that's an <span style="color: #e07a5f">**opportunity**</span> waiting for someone with enough coffee and determination!
|
113 |
|
114 |
+
### <span style="color: #e07a5f">Languages</span>
|
115 |
|
116 |
+
Primarily <span style="color: #81b29a">**US English**</span>, though you might encounter the occasional foreign phrase when companies get international. It's like <span style="color: #81b29a">*linguistic archaeology*</span> – you never know what you'll dig up.
|
117 |
|
118 |
+
## <span style="color: #e07a5f">Dataset Structure</span>
|
119 |
|
120 |
+
### <span style="color: #e07a5f">Data Instances</span>
|
121 |
|
122 |
+
Check out the data viewer for examples – trust me, it's more interesting than it sounds. Each instance is like a <span style="color: #81b29a">*little corporate story*</span> waiting to be told.
|
123 |
|
124 |
+
### <span style="color: #e07a5f">Data Fields</span>
|
125 |
+
|
126 |
+
Here's what each record contains <span style="color: #81b29a">*(because data dictionaries are love letters to future developers)*</span>:
|
127 |
|
128 |
| Field | Description |
|
129 |
|---|---|
|
130 |
+
| `index_html_url` | Filing index page *(your breadcrumb trail back to the source)* |
|
131 |
+
| `index_text_url` | Filing index text page *(for when HTML isn't your thing)* |
|
132 |
+
| `cik` | Central Index Key from EDGAR *(think of it as a company's social security number)* |
|
133 |
+
| `name` | Company name *(who's responsible for this legal masterpiece)* |
|
134 |
+
| `type` | Filing type *(10-K, 10-Q, or 8-K – the holy trinity of SEC filings)* |
|
135 |
+
| `date` | Filing date *(when this document saw the light of day)* |
|
136 |
+
| `seq` | Sequence number in the filing *(because order matters)* |
|
137 |
+
| `desc` | Description provided from the filing *(sometimes helpful, sometimes cryptic)* |
|
138 |
+
| `doc_type` | Document type (e.g. EX-10) *(the exhibit classification)* |
|
139 |
+
| `size` | Document size *(bigger isn't always better, but it usually means more billable hours)* |
|
140 |
+
| `filename` | Document name *(often more creative than you'd expect)* |
|
141 |
+
| `file_url` | Document page URL *(your direct line to the source)* |
|
142 |
+
| `file` | GCS file URI *(private, like a good secret)* |
|
143 |
+
| `__index_level_0__` | Please ignore *(the artifact of data wrangling we all pretend doesn't exist)* |
|
144 |
+
| `file_content` | Text content (HTML) or base64 string for binary content (PDF) *(the good stuff)* |
|
145 |
+
|
146 |
+
### <span style="color: #e07a5f">Data Splits</span>
|
147 |
+
|
148 |
+
There's no split by design – everything lives under <span style="color: #2c2c2c; background-color: #f4f3ee; padding: 2px 4px; border-radius: 3px;">`train`</span> because sometimes life is simpler that way. Feel free to create your own splits based on your specific needs <span style="color: #81b29a">*(and caffeine levels)*</span>.
|
149 |
|
150 |
+
## <span style="color: #e07a5f">Dataset Creation</span>
|
151 |
|
152 |
+
### <span style="color: #e07a5f">Curation Rationale</span>
|
153 |
|
154 |
+
Why spend <span style="color: #e07a5f">**sleepless nights**</span> building this dataset? Because SEC EDGAR is a <span style="color: #81b29a">**goldmine**</span> of publicly available corporate intelligence, and someone had to do the heavy lifting of making it ML-ready. This collection of exhibit files gives researchers direct access to the contracts and agreements that drive corporate decision-making – no more parsing through entire filings to find the good stuff.
|
155 |
|
156 |
+
### <span style="color: #e07a5f">Source Data</span>
|
157 |
|
158 |
+
https://www.sec.gov/ *<span style="color: #81b29a">(the government's gift to data scientists everywhere)</span>*
|
159 |
|
160 |
+
#### <span style="color: #e07a5f">Initial Data Collection and Normalization</span>
|
161 |
|
162 |
+
The data collection process was like archaeological excavation, but with more <span style="color: #81b29a">**Python**</span> and less dirt. We crawled through years of filings (10-K, 8-K, and 10-Q), extracting each exhibit individually with complete metadata. It's the kind of methodical, detail-oriented work that requires <span style="color: #e07a5f">multiple monitors</span> and a steady supply of debugging fuel.
|
163 |
|
164 |
+
Each document was downloaded with <span style="color: #81b29a">*surgical precision*</span>, preserving all metadata for maximum research utility. Think of it as digital preservation, but for corporate paperwork.
|
165 |
|
166 |
+
#### <span style="color: #e07a5f">Who are the source language producers?</span>
|
167 |
|
168 |
+
The unsung heroes behind this dataset are the army of <span style="color: #81b29a">**finance professionals, lawyers, and corporate executives**</span> who craft these documents. The SEC requires public companies, insiders, and broker-dealers to file these periodic statements, creating a continuous stream of corporate communication that investors and researchers rely on for informed decision-making.
|
169 |
|
170 |
+
These documents represent the <span style="color: #81b29a">*collective voice of corporate America*</span> – sometimes eloquent, sometimes bureaucratic, always fascinating from a linguistic perspective.
|
171 |
|
172 |
+
### Annotations
|
173 |
|
174 |
+
#### Annotation process
|
175 |
|
176 |
+
No additional annotations were added – we kept it pure and unadulterated, just the way the SEC intended.
|
177 |
|
178 |
+
#### Who are the annotators?
|
179 |
+
|
180 |
+
The original authors and their legal teams. Every comma placement was probably billable.
|
181 |
|
182 |
### Personal and Sensitive Information
|
183 |
|
184 |
+
Fair warning: this dataset might contain PII (names, emails, job titles, companies) that's already in the public domain. It comes with the territory when dealing with public filings – executives' names and contact information are part of the transparency requirements.
|
185 |
+
|
186 |
+
## <span style="color: #e07a5f">Considerations for Using the Data</span>
|
187 |
+
|
188 |
+
### <span style="color: #e07a5f">Social Impact of Dataset</span>
|
189 |
|
190 |
+
This dataset could be the catalyst for <span style="color: #81b29a">**better legal and finance language modeling capabilities**</span>. Imagine AI systems that can parse complex contracts, identify key terms, or help democratize access to legal understanding. Of course, with great power comes great responsibility – <span style="color: #e07a5f">*use it wisely*</span>.
|
191 |
|
192 |
+
### <span style="color: #e07a5f">Discussion of Biases</span>
|
193 |
|
194 |
+
Given the source and language, this dataset has a distinctly <span style="color: #81b29a">**US-centric flavor**</span> with a heavy dose of corporate legalese. It reflects the linguistic patterns and legal frameworks of American business culture, which might not translate well to other jurisdictions or informal contexts. Your model might end up sounding like it went to law school <span style="color: #81b29a">*(and accumulated the corresponding debt)*</span>.
|
195 |
|
196 |
+
### <span style="color: #e07a5f">Other Known Limitations</span>
|
197 |
|
198 |
+
Like any dataset scraped from the wild, this one has its quirks. PDF-to-text conversion isn't perfect, OCR sometimes gets <span style="color: #81b29a">*creative*</span>, and legal documents have their own special way of torturing the English language. Approach with realistic expectations and a <span style="color: #e07a5f">**good debugger**</span>.
|
199 |
|
200 |
+
## <span style="color: #e07a5f">Additional Information</span>
|
201 |
|
202 |
+
### <span style="color: #e07a5f">Dataset Curators</span>
|
203 |
|
204 |
+
@chenghao *<span style="color: #81b29a">(the sleep-deprived soul who made this possible)</span>*
|
205 |
|
206 |
+
### <span style="color: #e07a5f">Licensing Information</span>
|
207 |
|
208 |
+
[Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/) *<span style="color: #81b29a">(share and share alike, just the way open source should be)</span>*
|
209 |
|
210 |
+
### <span style="color: #e07a5f">Citation Information</span>
|
211 |
|
212 |
+
NA *<span style="color: #81b29a">(but feel free to give credit where credit is due)</span>*
|
213 |
|
214 |
+
### <span style="color: #e07a5f">Contributions</span>
|
215 |
|
216 |
+
This dataset exists thanks to countless hours of <span style="color: #e07a5f">**debugging**</span>, data wrangling, and the unwavering belief that good datasets make the world a better place. Special thanks to the SEC for maintaining EDGAR and making corporate transparency possible.
|
217 |
+
|
218 |
+
---
|
219 |
|
220 |
+
*<span style="color: #81b29a">Happy modeling! May your training runs be swift and your validation losses ever-decreasing.</span>* 🚀
|
221 |
|
222 |
+
**<span style="color: #e07a5f">sleepless</span><span style="color: #2c2c2c">@debugging:</span><span style="color: #81b29a">/datasets</span><span style="color: #2c2c2c">$</span> <span style="color: #e07a5f">█</span>**
|