feat(verify): batch 33 verified (491-488 new, 358 re-sourced); batch 02 decisions in progress

Checker: all five CLEAN. 393 cases now carry a verified summary and a
scenario sequence. Owner decisions recorded for batch 02 cases 211, 210,
208, 207, 206, 205 (batches/decide.py, corrections-approved.md); new
attribute proposed: prior acquaintance / insider. Report and export rebuilt.

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 13:10:43 +02:00
co-authored by Claude Fable 5.1
parent df95552208
commit 35e04201a6
19 changed files with 2513 additions and 98 deletions
+38 -23
View File
@@ -6,32 +6,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) | 389 |
| Cases with a scenario sequence (scenario-sequences.json) | 389 |
| Cases verified in batches 01–32 | 319 |
| Cases in the DB export | 393 |
| Cases with a verified summary (summary-overrides.json) | 393 |
| Cases with a scenario sequence (scenario-sequences.json) | 393 |
| Cases verified in batches 01–33 | 324 |
| 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
990 contradictions across 306 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
1007 contradictions across 310 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
| Field | Contradictions |
|---|---|
| description | 152 |
| date | 145 |
| description | 157 |
| date | 148 |
| amount | 95 |
| victim | 83 |
| location | 80 |
| attackers | 78 |
| money_wanted | 49 |
| weapons | 43 |
| victim | 84 |
| location | 81 |
| attackers | 79 |
| money_wanted | 50 |
| weapons | 44 |
| notes | 38 |
| arrests | 38 |
| detention | 37 |
| scenario | 36 |
| arrests | 35 |
| violence | 34 |
| violence | 35 |
| theft | 29 |
| coin_type | 17 |
| status | 11 |
@@ -50,6 +50,7 @@ Cases with the most contradictions (each needs a full re-entry):
- case 407 (William Sean "Tony" Creighton, CEO of 5Dimes): 10
- case 405 (David Princay, CEO of Binance France): 8
- case 358 (35 year old Chinese man): 8
- case 12 (Rocelo Lopes' wife): 7
- case 433 (Crypto Forum Moderator): 7
- case 412 (Mainland Chinese businessman, 25): 7
@@ -67,15 +68,14 @@ Cases with the most contradictions (each needs a full re-entry):
- case 403 (Male cryptocurrency holder): 6
- case 402 (Two adults): 6
- case 201 (Stéphane Winkel's Wife): 5
- case 200 (Benjamin Appiah Boateng): 5
## Flag proposals
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.
418 proposals on 224 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 |
|---|---|---|---|
| drugs_alcohol | null | 0 | 81 |
| drugs_alcohol | null | 0 | 85 |
| drugs_alcohol | 1 | unconfirmed | 4 |
| drugs_alcohol | 0 | unverified | 4 |
| drugs_alcohol | 0 | 1 | 2 |
@@ -94,7 +94,7 @@ Cases with the most contradictions (each needs a full re-entry):
| life_taken | 1 | unconfirmed | 1 |
| theft | 0 | 1 | 16 |
| theft | 1 | unconfirmed | 14 |
| theft | null | unconfirmed | 7 |
| theft | null | unconfirmed | 8 |
| theft | 1 | 0 | 4 |
| theft | null | 0 | 4 |
| theft | 1 | unverified | 3 |
@@ -156,14 +156,14 @@ Label frequency across all sequences:
| Label | Uses |
|---|---|
| Kidnapping | 132 |
| Home Invasion | 110 |
| Home Invasion | 113 |
| Malicious Invitation - SocialEng | 66 |
| Dodged Attack | 55 |
| P2P Trade Gone Wrong | 36 |
| Authority Misuse | 33 |
| Armed Robbery in Public Space | 25 |
| Costly Fame | 19 |
| Express Kidnapping | 17 |
| Express Kidnapping | 18 |
| Assault - Mugging | 8 |
| Swatting | 2 |
@@ -205,19 +205,19 @@ Gap notes grouped by theme. Counts are notes, not cases; a case can raise severa
| 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) | 11 | 15, 53, 60, 110, 157, 162, 181, 200, 213, 215, 461 |
| 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 |
| Preparation: leaks, surveillance, trackers, data breaches | 18 | 83, 91, 121, 123, 133, 145, 183, 184, 185, 384, 422, 445, 446, 453, 469, 472, 490 |
| 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 | 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 |
| Multiple victims, proxy victims or one victim field | 10 | 23, 24, 26, 39, 74, 387, 401, 404, 427, 431 |
| Amount and coin fields cannot split crypto from cash, goods or fiat | 20 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 181, 188, 254, 255, 357, 384, 407, 412, 465, 471, 486 |
| Amount and coin fields cannot split crypto from cash, goods or fiat | 22 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 181, 188, 254, 255, 357, 358, 384, 407, 412, 465, 471, 486, 490 |
| Control moves between places; one venue field | 5 | 5, 401, 412, 444, 460 |
| Outcome after the transfer (killing, escape, rescue) is not an initiation label | 9 | 52, 84, 147, 166, 201, 361, 366, 432, 458 |
| Crypto link or complainant account is itself unverified | 7 | 96, 175, 178, 199, 399, 400, 443 |
| Initiation or entry method not reported | 7 | 141, 156, 223, 409, 454, 477, 485 |
| Remote operator, phone drained after the event, or company infrastructure | 4 | 28, 164, 196, 211 |
| Other | 407 | 1, 3, 4, 5, 7, 8, 11, 12, 13, 14, 15, 16, 18, 19, 20, 22, 23, 24, 25, 27, 28, 29, 30, 32, 33, 34, 35, 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, 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, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 197, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 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, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487 |
| Other | 419 | 1, 3, 4, 5, 7, 8, 11, 12, 13, 14, 15, 16, 18, 19, 20, 22, 23, 24, 25, 27, 28, 29, 30, 32, 33, 34, 35, 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, 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, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 197, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 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, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491 |
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).
@@ -430,6 +430,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 453: surveillance of the victim's daughter is recorded nowhere
- case 469: an attack stopped by police who knew about it beforehand has no label of its own; Dodged Attack covers victim awareness and luck as much as prior intelligence
- case 472: a wrong-target attack, where the leaked address rather than the occupants was the target, has no label
- case 490: the household was picked from a leaked tax-reporting file, and no field records how the victims were selected
### Drugging as the approach
@@ -511,12 +512,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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 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 357: the £450,000 watch was the larger single loss and no field separates it from the crypto
- case 358: the amounts arrive in four currencies across the three reports (baht, USDT, dollars, won) and there is one amount field
- case 384: no cryptocurrency was taken — the loss was 1 billion yen in banknotes and the crypto nexus is the victims' employer's line of business, which coin_type can only record as '4 briefcases with cash'
- case 407: a ransom paid in part and a victim killed anyway has no field; the record's money_wanted carries both numbers in prose
- case 412: a theft of physical goods (silver) alongside the crypto has no field of its own; the record puts it in coin_type
- case 465: the £250,000 covers a watch and bitcoin together; the amount fields cannot express a combined loss
- case 471: the record's 'remote mastermind' watching the Snapchat stream appears in no article on file
- case 486: the record cannot hold the split between the crypto ($562,155) and the jewellery (about $413,500)
- case 490: the haul splits three ways - about 100 euros in crypto, two bank transfers of 450 euros and stolen goods - and there is one amount field
### Control moves between places; one venue field
@@ -799,6 +802,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 352: a man killed while resisting and one of the attackers killed by a defender sit together in a single life_taken count of 2
- case 352: a third person, the brother-in-law who came with a gun, was shot and wounded and no field records him
- case 357: the two reports disagree on whether the victims or the robbers were the ones left in Five Mile Drive, and no field records that
- case 358: roughly two hours of detention in a car and a car park ending in release once the reachable funds were gone reads as Express Kidnapping as much as Kidnapping, and only one label can be recorded
- case 358: the crew's claim that they were collecting an unpaid debt, and the victim's disputed relationship with the lead suspect, have no field
- case 358: the report does not say how long the man was held
- case 358: the snatch, the short hold and the release after the transfer also match Express Kidnapping, and only one label can be carried
- case 358: the suspect's claim that he was recovering a debt is a disputed motive no field records
@@ -974,6 +979,16 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 486: a victim who escaped from a robbery that had already succeeded has no outcome that fits cleanly
- case 487: nothing records how the pair got free after the attackers fled
- case 487: what was taken was the credentials, not the coins: the phone held the access codes and no source says the account was emptied, which the theft flag cannot distinguish
- case 488: an abduction attempt that fails inside a completed home invasion has no label, and the file supports neither a Kidnapping nor a Dodged Attack reading
- case 488: her connection to cryptoassets is undisclosed; the record's victim field is only 'Woman'
- case 488: no source says whether anything was taken, so the theft flag cannot be set either way
- case 489: a 12-year-old struck to make the father comply has no field of its own
- case 489: a fifth person coaching the crew by phone throughout, allegedly in Arabic so the family could not follow, has no field
- case 489: how the attackers learned that this household held crypto is the open question in the file and no field records targeting
- case 490: an organiser running the job from a prison cell has no field
- case 491: a lookout phoning the crew a police warning is the detail that ended the captivity and no field holds it
- case 491: the only crypto element is an attempted "Cripto-Pix" operation, and the record's crypto fields cannot say "attempted, amount unknown"
- case 491: the snatch and the captivity happened in two different municipalities (Jundiai and Campo Limpo Paulista, per A Voz de Jundiai) and there is one location field
## Cases to decide on scope, merge or split