# Datasets and using pre-annotated data

**URL:** <https://support.prodi.gy/t/datasets-and-using-pre-annotated-data/1476>\
**Category:** Getting Started\
**Tags:** usage, solved\
**Created:** [May 3, 2019, 11:12am UTC](https://support.prodi.gy/t/datasets-and-using-pre-annotated-data/1476 "2019-05-03T11:12:06Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ines](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/ines/32/3_2.png) [@ines](https://support.prodi.gy/u/ines)\
**Post date:** [May 3, 2019, 3:49pm UTC](https://support.prodi.gy/t/datasets-and-using-pre-annotated-data/1476/4 "2019-05-03T15:49:17Z")

</div>

If you look at the “Annotation task formats” section in your `PRODIGY_README.html`, you’ll find the exact JSON format that Prodigy expects for pre-annotated data for the different annotation types (NER, text classification etc.). The format should be pretty straightforward: for each example, you usually have a `"text"` and then either a `"label"` or `"spans"`, depending on what you’re annotating. You can then convert your pre-annotated data accordingly. For example, for named entity recognition, you’ll need the text and the start/end character offsets and labels for the entities in that text.

---

_[View the full topic](https://support.prodi.gy/t/datasets-and-using-pre-annotated-data/1476)._