feat(verify): batch 32 verified (257-109); verification complete for all 389 cases

Checker: five CLEAN, four minor fixes (255 evidence wording, 209 flag count
and source hedge plus the Vierzon/Bourges brigade discrepancy, 188 arrest
timing, 109 contradiction attribution). summary-overrides.json and
scenario-sequences.json now hold one entry per DB case. Report and export
regenerated.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZZENdTLzNGsbNy4DyF1yt
This commit is contained in:
StellarCrow
2026-09-30 12:34:49 +02:00
co-authored by Claude Fable 5.1
parent c9d6a0f2fd
commit 6cfa0b19c9
19 changed files with 1506 additions and 153 deletions
+67 -39
View File
@@ -7,32 +7,32 @@ Every summary, scenario sequence, flag proposal and contradiction below was writ
| Item | Count |
|---|---|
| Cases in the DB export | 389 |
| Cases with a verified summary (summary-overrides.json) | 380 |
| Cases with a scenario sequence (scenario-sequences.json) | 380 |
| Cases verified in batches 01–31 | 310 |
| Cases still without a verified summary | 9 [109, 177, 188, 203, 209, 223, 254, 255, 257] |
| Cases with a verified summary (summary-overrides.json) | 389 |
| Cases with a scenario sequence (scenario-sequences.json) | 389 |
| Cases verified in batches 01–32 | 319 |
| Cases still without a verified summary | 0 |
| Record-only cases (no usable article on file) | 4 [11, 45, 66, 399] |
## Contradictions between record and articles
952 contradictions across 298 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
991 contradictions across 307 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
| Field | Contradictions |
|---|---|
| description | 149 |
| date | 140 |
| amount | 91 |
| victim | 78 |
| location | 77 |
| attackers | 73 |
| money_wanted | 44 |
| weapons | 41 |
| description | 153 |
| date | 145 |
| amount | 95 |
| victim | 83 |
| location | 80 |
| attackers | 78 |
| money_wanted | 49 |
| weapons | 43 |
| notes | 38 |
| detention | 36 |
| scenario | 35 |
| arrests | 34 |
| violence | 32 |
| theft | 28 |
| detention | 37 |
| scenario | 36 |
| arrests | 35 |
| violence | 34 |
| theft | 29 |
| coin_type | 17 |
| status | 11 |
| site summary | 8 |
@@ -55,6 +55,7 @@ Cases with the most contradictions (each needs a full re-entry):
- case 412 (Mainland Chinese businessman, 25): 7
- case 411 (Igor Komarov): 7
- case 408 (Yong Wang, Chinese businessman ): 7
- case 209 (David Balland & Wife): 7
- case 199 (Igor Lermakov): 6
- case 32 (Shailesh Bhatt): 6
- case 23 (T.W. (Troy Woody Jr.)): 6
@@ -67,11 +68,10 @@ Cases with the most contradictions (each needs a full re-entry):
- case 402 (Two adults): 6
- case 201 (Stéphane Winkel's Wife): 5
- case 200 (Benjamin Appiah Boateng): 5
- case 180 (Chinese National): 5
## Flag proposals
402 proposals on 213 cases (batches/flag-proposals.json). 'unconfirmed' means no source on file supports the recorded value; 'threat only' means a weapon or violence was threatened, not used.
413 proposals on 220 cases (batches/flag-proposals.json). 'unconfirmed' means no source on file supports the recorded value; 'threat only' means a weapon or violence was threatened, not used.
| Flag | Record | Proposed | Count |
|---|---|---|---|
@@ -80,7 +80,7 @@ Cases with the most contradictions (each needs a full re-entry):
| drugs_alcohol | 0 | unverified | 4 |
| drugs_alcohol | 0 | 1 | 2 |
| drugs_alcohol | 1 | 0 | 2 |
| kidnappings | 0 | 1 | 40 |
| kidnappings | 0 | 1 | 42 |
| kidnappings | 1 | 0 | 6 |
| kidnappings | 1 | unconfirmed | 4 |
| kidnappings | null | 0 | 3 |
@@ -92,7 +92,7 @@ Cases with the most contradictions (each needs a full re-entry):
| life_taken | null | 0 | 2 |
| life_taken | 0 | 1 | 1 |
| life_taken | 1 | unconfirmed | 1 |
| theft | 0 | 1 | 15 |
| theft | 0 | 1 | 16 |
| theft | 1 | unconfirmed | 14 |
| theft | null | unconfirmed | 9 |
| theft | 1 | 0 | 4 |
@@ -100,20 +100,21 @@ Cases with the most contradictions (each needs a full re-entry):
| theft | 1 | unverified | 3 |
| theft | 0 | unverified | 1 |
| theft | null | 1 | 1 |
| violence_torture | 0 | 1 | 23 |
| theft | 0 | unconfirmed | 1 |
| violence_torture | 0 | 1 | 25 |
| violence_torture | null | 0 | 16 |
| violence_torture | 1 | threat only | 6 |
| violence_torture | 1 | 0 | 6 |
| violence_torture | null | unconfirmed | 6 |
| violence_torture | 1 | unconfirmed | 5 |
| violence_torture | null | unconfirmed | 5 |
| violence_torture | 0 | unconfirmed | 3 |
| violence_torture | null | 1 | 3 |
| violence_torture | 0 | unverified | 2 |
| violence_torture | null | threat only | 2 |
| violence_torture | 1 | unverified | 2 |
| weapons | 0 | 1 | 32 |
| weapons | null | 0 | 31 |
| weapons | 0 | 1 | 30 |
| weapons | 1 | unconfirmed | 20 |
| weapons | 1 | unconfirmed | 22 |
| weapons | 1 | 0 | 12 |
| weapons | null | 1 | 9 |
| weapons | null | unconfirmed | 8 |
@@ -122,7 +123,7 @@ Cases with the most contradictions (each needs a full re-entry):
| weapons | 0 | unconfirmed | 1 |
| weapons | 1 | unconfirmed for this incident | 1 |
Detention (DB field kidnappings) 0/null → 1 under the owner's rule (40): [4, 8, 19, 20, 25, 28, 29, 33, 41, 42, 43, 46, 63, 64, 77, 82, 90, 93, 139, 143, 147, 152, 164, 167, 169, 171, 180, 181, 182, 183, 185, 197, 200, 241, 380, 405, 417, 479, 483, 486]
Detention (DB field kidnappings) 0/null → 1 under the owner's rule (42): [4, 8, 19, 20, 25, 28, 29, 33, 41, 42, 43, 46, 63, 64, 77, 82, 90, 93, 109, 139, 143, 147, 152, 164, 167, 169, 171, 180, 181, 182, 183, 185, 197, 200, 209, 241, 380, 405, 417, 479, 483, 486]
Detention 1 → 0 (6): [124, 128, 151, 195, 406, 423]
@@ -144,19 +145,19 @@ Fatality flag (life_taken) proposals:
| Item | Count |
|---|---|
| Cases with more than one label in sequence | 126 |
| Cases where the v1 label is not supported by the file | 59 |
| Foiled attacks (Dodged Attack) | 53 |
| Cases with more than one label in sequence | 130 |
| Cases where the v1 label is not supported by the file | 60 |
| Foiled attacks (Dodged Attack) | 55 |
| Cases no label fits (empty sequence) | 23 |
Label frequency across all sequences:
| Label | Uses |
|---|---|
| Kidnapping | 127 |
| Home Invasion | 103 |
| Kidnapping | 131 |
| Home Invasion | 110 |
| Malicious Invitation - SocialEng | 66 |
| Dodged Attack | 53 |
| Dodged Attack | 55 |
| P2P Trade Gone Wrong | 36 |
| Authority Misuse | 33 |
| Armed Robbery in Public Space | 26 |
@@ -197,18 +198,18 @@ Gap notes grouped by theme. Counts are notes, not cases; a case can raise severa
| Theme | Notes | Cases |
|---|---|---|
| Repeat victimisation / several incidents on one record | 37 | 9, 18, 32, 38, 49, 72, 106, 134, 162, 169, 179, 184, 185, 259, 354, 355, 357, 374, 395, 423, 436, 439, 440, 441, 446, 463, 466, 467, 470, 471, 472, 483, 487 |
| Insider, intimate or acquaintance perpetrator | 40 | 13, 21, 33, 43, 46, 59, 69, 70, 81, 97, 108, 116, 130, 139, 152, 153, 170, 179, 186, 194, 204, 212, 373, 376, 385, 386, 391, 396, 407, 444, 447, 448, 451, 454, 455, 457, 458, 475, 486 |
| Repeat victimisation / several incidents on one record | 42 | 9, 18, 32, 38, 49, 72, 106, 134, 162, 169, 179, 184, 185, 203, 209, 223, 254, 257, 259, 354, 355, 357, 374, 395, 423, 436, 439, 440, 441, 446, 463, 466, 467, 470, 471, 472, 483, 487 |
| Insider, intimate or acquaintance perpetrator | 41 | 13, 21, 33, 43, 46, 59, 69, 70, 81, 97, 108, 116, 130, 139, 152, 153, 170, 179, 186, 194, 204, 212, 257, 373, 376, 385, 386, 391, 396, 407, 444, 447, 448, 451, 454, 455, 457, 458, 475, 486 |
| Empty premises, unattended machines, infrastructure | 41 | 2, 3, 6, 10, 11, 19, 21, 38, 51, 54, 57, 62, 66, 71, 84, 85, 101, 102, 105, 112, 158, 198, 352, 383, 389, 399, 420, 449, 450 |
| Extortion at a distance or threat at the door without entry | 13 | 44, 133, 139, 144, 190, 318, 354, 355, 403, 412, 419, 423, 457 |
| Lured to and held at the attackers' venue (captivity without transport) | 10 | 15, 53, 60, 110, 157, 162, 181, 200, 213, 461 |
| Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation) | 23 | 50, 90, 93, 104, 117, 150, 164, 182, 184, 185, 258, 360, 385, 402, 413, 429, 438, 442, 444, 447, 448, 451, 479 |
| Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation) | 24 | 50, 90, 93, 104, 109, 117, 150, 164, 182, 184, 185, 258, 360, 385, 402, 413, 429, 438, 442, 444, 447, 448, 451, 479 |
| Preparation: leaks, surveillance, trackers, data breaches | 17 | 83, 91, 121, 123, 133, 145, 183, 184, 185, 384, 422, 445, 446, 453, 469, 472 |
| Drugging as the approach | 4 | 48, 88, 92, 97 |
| Unexplained death or undetermined circumstances | 12 | 26, 58, 207, 295, 392, 400, 443, 467, 468, 485 |
| Security measures deciding the outcome | 6 | 126, 186, 439, 440, 441, 473 |
| Security measures deciding the outcome | 7 | 126, 186, 257, 439, 440, 441, 473 |
| Scope: fraud, non-violent, or not crypto-linked | 16 | 8, 18, 27, 39, 42, 56, 61, 73, 83, 89, 94, 137, 150, 260, 394, 398 |
| Other | 451 | 1, 3, 4, 5, 7, 8, 9, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 39, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 84, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 110, 111, 113, 114, 116, 117, 118, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 164, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 178, 179, 180, 181, 182, 183, 189, 190, 193, 194, 195, 196, 197, 199, 200, 201, 202, 205, 206, 207, 208, 210, 211, 215, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 384, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 444, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 471, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487 |
| Other | 470 | 1, 3, 4, 5, 7, 8, 9, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 39, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 84, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 114, 116, 117, 118, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 164, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 188, 189, 190, 193, 194, 195, 196, 197, 199, 200, 201, 202, 203, 205, 206, 207, 208, 209, 210, 211, 215, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 384, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 444, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 471, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487 |
Proposed additions to the vocabulary, in order of how often the gap appears: (1) a `repeat_victimisation` / campaign link between records; (2) an `insider` initiation attribute (relative, partner, driver, guard, friend); (3) a label for attacks on unattended premises and machines (burglary, ATM ram-raid, mining rigs); (4) remote extortion with threat but no contact; (5) 'held at attackers' venue' as a Kidnapping sub-type; (6) a `ruse` attribute (delivery, uniform, disguise) separate from Authority Misuse and Malicious Invitation; (7) a preparation phase field (leak, surveillance, tracker).
@@ -228,6 +229,11 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 179: repeat victimisation is carried on one record: the article also reports a similar incident by another man on 4 June 2024 and a break-in at the victim's home on 17 July
- case 184: the later Telegram extortion is a second event carried on the same record
- case 185: eleven victims robbed in one event are carried on a single record
- case 203: three people held at the house and one driven hundreds of kilometres away sit on one record with one scenario field
- case 209: two victims held at two separate locations about 200 kilometres apart sit on one record with one location field
- case 223: two victims, one of them an employee killed alongside his principal, sit on one record
- case 254: the follow-up extortion call two days later is a second event held inside one record with one date
- case 257: two households entered in one operation are held as one record, with one location and one victim field
- case 259: two victims sit on one record: life_taken carries the 2 and nothing else distinguishes them
- case 354: repeat victimisation across a campaign has no label
- case 355: repeat victimisation across a months-long campaign has no label
@@ -276,6 +282,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 194: held in a third party's hotel room after a visit to a friend, never moved: tagged Kidnapping by the convention for captivity at someone else's premises
- case 204: an extortion growing out of a prior business dispute between acquaintances has no label
- case 212: an intimate partner or family member as the organiser has no label; Malicious Invitation is used for the betrayal of trust
- case 257: the attack was ended by relatives arriving, not by police, and no field records who broke it off
- case 373: the person held is a relative of the presumed asset holder, not the holder: extortion of a family member through a proxy victim has no label
- case 376: a relative as the organiser of the abduction has no label
- case 385: the ransom was paid from another country by a relative who was never in danger himself, which the money fields cannot show
@@ -374,6 +381,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 90: a false-technician pretext used to get a door opened is not the corrupt-official or fake-police case Authority Misuse is written around, but it is the same mechanism of borrowed legitimacy
- case 93: detention in a real police cell by serving officers, under colour of a bail demand, has no label; Authority Misuse covers the pretext and Express Kidnapping the same-night extraction, but neither says the holding place was a police station
- case 104: the pretext was a crypto transaction, so P2P Trade Gone Wrong fits the initiation as well as Malicious Invitation; the single-label rule forces a choice
- case 109: a fake parcel delivery used to get through the door has no label of its own
- case 117: police call the plan pre-arranged from the start, which makes the crypto account an invented pretext rather than a trade that went wrong
- case 150: one attacker wore a police uniform, an Authority Misuse element, but neither source says the uniform was used to gain entry
- case 164: entry gained by pretext (posing as colleagues) rather than by force has no label; Armed Robbery covers the theft but not the deception
@@ -440,6 +448,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 126: who raised the alarm at 5 a.m., and how the couple got free, is not in the file, so no outcome value can be supported
- case 186: the CCTV servers and the victim's car taken alongside the crypto transfer are not expressible in the scenario label
- case 257: a game-chat microphone used as an alarm is the interesting detail here and no field holds it
- case 439: security measures deciding the outcome is the whole substance of the case and nothing records it
- case 440: security measures deciding the outcome is the whole substance of the case and nothing records it
- case 441: security measures deciding the outcome is the whole substance of the case and nothing records it
@@ -606,6 +615,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 105: force used against bystanders during the getaway, rather than against a victim, has nowhere to go in the schema
- case 106: a private client renting real police power — badges, databases, sworn warrants — has no label beyond Authority Misuse
- case 108: the password was extracted by threatening the wife rather than the man being held; coercion through a third person has no label
- case 109: an attack the victim faced down inside his own home is both Home Invasion and Dodged Attack, and the record's single field holds neither
- case 109: the attack was broadcast live to 2,000 viewers, which is the distinguishing fact of the case and has no field
- case 110: extortion of one inmate by others inside a jail, with correctional officers ending it, has no label of its own
- case 111: a part-paid ransom traced on-chain to make the arrests has no label; nor does the victim's fate, which the report leaves open
- case 111: the labels cannot express that the official trappings were faked with a green plate while three of the accused were genuine police officials
@@ -675,6 +686,9 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 176: eleven people robbed at once in a private unit with no restraint described fits neither the public-space robbery label nor the Home Invasion definition's hostage-holding element
- case 176: the report does not say whether the residential unit was any victim's home, so the venue behind the Home Invasion label is uncertain
- case 176: victims who are themselves suspected of running a gambling ring have no place in the labels
- case 177: how the attackers learned his address and that he held crypto is the question the case turns on, and no field holds it
- case 177: the record gives no duration and neither does the article
- case 177: the whole case rests on the victim's own posts relayed by one outlet, with no police or court source, and no field records that
- case 178: the crypto connection here is the ransom currency alone — the reports do not say the family were crypto holders
- case 178: the victim is a child and the ransom target is someone else; the labels have no way to separate the person held from the person extorted
- case 179: extortion leveraging the victim's own illegal earnings ('he was afraid I would file a complaint') is not expressible
@@ -683,6 +697,9 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 181: a crypto trader robbed of phones, watches, a card and cash with no crypto reported taken does not fit the database's crypto-loss framing
- case 182: a forced transfer carried out on the victim's own seized phone is not expressible in the labels
- case 183: the murder after the transfer is the outcome, not the initiation pattern, and the scenario label cannot carry it
- case 188: a kidnapping that lasted from one crash to the next, minutes rather than hours, reads the same in the labels as a week-long captivity
- case 188: the people held were leverage against their son, and no field records that the target was someone else
- case 188: the record's crypto figure belongs to a separate online theft a week earlier, not to this attack, and the schema has one amount field
- case 189: an attack that landed an assault but failed at the theft sits between Dodged Attack and a completed robbery; the labels force a choice
- case 190: the record's single Home Invasion label loses the five days of captivity at two other addresses
- case 193: neither source says where he was held or for how long, so Express Kidnapping can be neither ruled in nor out
@@ -696,13 +713,24 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 200: the record carries one victim name for a case with two detainees; Boateng's own detention at Laboma Beach from 14 December is not expressed
- case 201: VRT calls it an attempted or failed abduction because no ransom was obtained, although she was taken in a car as far as Bruges; no label marks an abduction interrupted in progress
- case 202: a detention of about two hours in a police vehicle that ends in release as soon as the transfer clears sits between Express Kidnapping and Authority Misuse; only one label can be primary
- case 203: the extortion target was the son abroad, not any of the people held, and no field records that
- case 203: the two articles disagree on whether the partner was taken in the car or left tied at the house, and the victim field cannot hold the doubt
- case 205: the plot was broken by an informant inside the group chat, not by anything the victim did; Dodged Attack carries a suggestion of victim awareness that this case does not support
- case 206: police suspect the victim knew his attackers, which no label captures; how the three got into the room is not stated
- case 207: where he was held during the three days is not stated; he only heard he was to be taken to Antipolo City
- case 208: a series of genuine trades used to build trust before the theft has no label
- case 209: a ransom paid, then frozen and seized, is a theft that was largely undone, and the theft flag cannot say so
- case 209: the extortion target was a third party, another Ledger co-founder, not either of the people held
- case 210: the file does not say whether the house where he was held was the meeting place itself or somewhere he was taken to; Kidnapping is used for captivity on premises that are not his
- case 211: the attackers operated the victims' phones themselves while a third party coached them by telephone; no label expresses the remote-operator role
- case 215: a killing during a trade in a hotel room; Armed Robbery is the label for weapon-plus-theft, with the P2P trade as the initiation
- case 223: a ransom paid twice and the hostages killed anyway has no field; the outcome column can only say killed
- case 223: the record's initiation - a woman used to lure the businessman to a house - appears in no article on file, so the label rests on the police account of a house in Meycauayan
- case 254: a demand of 500 BTC against a take of about $600,000 has one amount field, and the record used it for the take
- case 254: the laundering leg through HTX and Kyrrex has no field
- case 255: a remote third party feeding account information to the men in the house by phone has no field
- case 255: the husband was driven three hours to a second property and forced to transfer there, a kidnapping leg inside a home invasion that one scenario field cannot carry
- case 255: the loss runs from at least $72,000 in the charging documents to $8 million in the prosecutors' statement, and there is one amount field
- case 258: police say there were at least five participants and only three are accounted for
- case 258: the cash loss of 14,600 euros and the crypto loss of more than 83,000 dollars sit in one money field, and the record carries only the crypto
- case 258: the victim was handling other people's funds, which is the reason police give for his being targeted, and no field records it
@@ -924,6 +952,6 @@ No scenario label fits (mostly empty premises, unattended machines and burglarie
Writer questioned scope for another reason (not crypto-related, lawful entry, doxing only, argument during a sale, non-violent device theft): [5, 21, 24, 45, 58, 70, 122, 123, 173, 195, 383, 400, 435, 483]
Possible merges or splits (same incident across records, or several incidents on one record): [38, 89, 318, 398, 439, 440, 441, 445, 446, 457, 459]
Possible merges or splits (same incident across records, or several incidents on one record): [38, 89, 255, 318, 398, 439, 440, 441, 445, 446, 457, 459]
Record-only (restructured from the DB record; nothing to verify against): [11, 45, 66, 399]