Discrepancy between README and v1.1 data.

Hi,
I've noticed that starting at 2025-04 the format of the reference organizations does not match the README. I believe this change was introduced in cfac6a7f3c5901a68104d6cff479fdc708ab8462.

Before this, the `Reference Orgs` field contains dictionaries (example AS1 from 2025-03):
```json
[
{
"name": "Central Host, Inc.",
"org_id": "873",
"source": "PDB"
},
{
"name": "CenturyLink Communications, LLC",
"source": "Whois"
},
{
"name": "LUMEN TECHNOLOGIES UK LIMITED",
"source": "Whois"
},
{
"name": "Level 3 Parent, LLC",
"org_id": "38227",
"source": "PDB"
},
{
"name": "Level 3 Parent, LLC",
"source": "Whois"
},
{
"name": "LightCore a CenturyTel Co.",
"org_id": "1526",
"source": "PDB"
},
{
"name": "Lumen Technologies Inc",
"org_id": "682",
"source": "PDB"
}
]
```

But after this it seems that the dictionaries were replaced by prefixed strings (example AS1 from 2025-04):

```json
[
"PDB: Central Host, Inc.",
"Whois: CenturyLink Communications, LLC",
"Whois: LUMEN TECHNOLOGIES UK LIMITED",
"Whois: Level 3 Parent, LLC",
"PDB: LightCore a CenturyTel Co.",
"PDB: Lumen Technologies Inc"
]
```

This format is slightly more complicated to parse and also loses information about the PeeringDB ID. If this is intentional, the README should be updated to reflect this (although I prefer the format in the current README :)).

Start by comparing the README's Reference Orgs example with the v1.1 data for 2025-03 and 2025-04, then inspect commit cfac6a7f3c5901a68104d6cff479fdc708ab8462. Confirm whether the prefixed-string format is intentional and whether PeeringDB IDs should remain available; done means the README and published data format agree, or the discrepancy is corrected.

Written by the indexing model from the issue text.