Archived
feat(verify): batch 34 verified (496-492); owner decisions to 121
Checker: four CLEAN, 492 Authority Misuse removed (legend not shown at the point of contact). 398 cases now carry verified summaries and sequences. Possible same-gang link 492/258 noted for the owner. 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:
co-authored by
Claude Fable 5.1
parent
43edfeb018
commit
ef8d064fd0
@@ -6,38 +6,38 @@ Every summary, scenario sequence, flag proposal and contradiction below was writ
|
||||
|
||||
| Item | Count |
|
||||
|---|---|
|
||||
| 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 in the DB export | 398 |
|
||||
| Cases with a verified summary (summary-overrides.json) | 398 |
|
||||
| Cases with a scenario sequence (scenario-sequences.json) | 398 |
|
||||
| Cases verified in batches 01–34 | 329 |
|
||||
| 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
|
||||
|
||||
1007 contradictions across 310 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
|
||||
1007 contradictions across 314 cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.
|
||||
|
||||
| Field | Contradictions |
|
||||
|---|---|
|
||||
| description | 157 |
|
||||
| date | 148 |
|
||||
| amount | 95 |
|
||||
| description | 155 |
|
||||
| date | 147 |
|
||||
| amount | 96 |
|
||||
| victim | 84 |
|
||||
| location | 81 |
|
||||
| attackers | 79 |
|
||||
| money_wanted | 50 |
|
||||
| weapons | 44 |
|
||||
| notes | 38 |
|
||||
| location | 82 |
|
||||
| attackers | 80 |
|
||||
| money_wanted | 51 |
|
||||
| weapons | 43 |
|
||||
| arrests | 38 |
|
||||
| notes | 37 |
|
||||
| detention | 37 |
|
||||
| scenario | 36 |
|
||||
| violence | 35 |
|
||||
| theft | 29 |
|
||||
| scenario | 37 |
|
||||
| violence | 36 |
|
||||
| theft | 30 |
|
||||
| coin_type | 17 |
|
||||
| status | 11 |
|
||||
| status | 10 |
|
||||
| site summary | 8 |
|
||||
| flags | 7 |
|
||||
| drugs_alcohol | 6 |
|
||||
| drugs_alcohol | 5 |
|
||||
| victims | 1 |
|
||||
| location of the abduction | 1 |
|
||||
| location of arrest | 1 |
|
||||
@@ -71,14 +71,14 @@ Cases with the most contradictions (each needs a full re-entry):
|
||||
|
||||
## Flag proposals
|
||||
|
||||
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.
|
||||
429 proposals on 230 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 | 85 |
|
||||
| drugs_alcohol | null | 0 | 90 |
|
||||
| drugs_alcohol | 1 | unconfirmed | 4 |
|
||||
| drugs_alcohol | 0 | unverified | 4 |
|
||||
| drugs_alcohol | 0 | 1 | 2 |
|
||||
| drugs_alcohol | 0 | 1 | 4 |
|
||||
| drugs_alcohol | 1 | 0 | 2 |
|
||||
| kidnappings | 0 | 1 | 42 |
|
||||
| kidnappings | 1 | 0 | 6 |
|
||||
@@ -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 | 16 |
|
||||
| theft | 0 | 1 | 17 |
|
||||
| theft | 1 | unconfirmed | 14 |
|
||||
| theft | null | unconfirmed | 8 |
|
||||
| theft | 1 | 0 | 4 |
|
||||
@@ -102,7 +102,7 @@ Cases with the most contradictions (each needs a full re-entry):
|
||||
| theft | 0 | unverified | 1 |
|
||||
| theft | 0 | unconfirmed | 1 |
|
||||
| theft | null | 1 (inferred) | 1 |
|
||||
| violence_torture | 0 | 1 | 25 |
|
||||
| violence_torture | 0 | 1 | 26 |
|
||||
| violence_torture | null | 0 | 16 |
|
||||
| violence_torture | 1 | threat only | 6 |
|
||||
| violence_torture | 1 | 0 | 6 |
|
||||
@@ -113,8 +113,9 @@ Cases with the most contradictions (each needs a full re-entry):
|
||||
| violence_torture | 0 | unverified | 2 |
|
||||
| violence_torture | null | threat only | 2 |
|
||||
| violence_torture | 1 | unverified | 2 |
|
||||
| violence_torture | null | 0 (threat and restraint only) | 1 |
|
||||
| weapons | 0 | 1 | 32 |
|
||||
| weapons | null | 0 | 31 |
|
||||
| weapons | null | 0 | 32 |
|
||||
| weapons | 1 | unconfirmed | 22 |
|
||||
| weapons | 1 | 0 | 12 |
|
||||
| weapons | null | 1 | 9 |
|
||||
@@ -146,20 +147,20 @@ Fatality flag (life_taken) proposals:
|
||||
|
||||
| Item | Count |
|
||||
|---|---|
|
||||
| Cases with more than one label in sequence | 150 |
|
||||
| Cases where the v1 label is not supported by the file | 50 |
|
||||
| Foiled attacks (Dodged Attack) | 55 |
|
||||
| Cases with more than one label in sequence | 152 |
|
||||
| Cases where the v1 label is not supported by the file | 49 |
|
||||
| Foiled attacks (Dodged Attack) | 56 |
|
||||
| Cases no label fits (empty sequence) | 23 |
|
||||
|
||||
Label frequency across all sequences:
|
||||
|
||||
| Label | Uses |
|
||||
|---|---|
|
||||
| Kidnapping | 132 |
|
||||
| Home Invasion | 113 |
|
||||
| Kidnapping | 133 |
|
||||
| Home Invasion | 115 |
|
||||
| Malicious Invitation - SocialEng | 66 |
|
||||
| Authority Misuse | 62 |
|
||||
| Dodged Attack | 55 |
|
||||
| Authority Misuse | 65 |
|
||||
| Dodged Attack | 56 |
|
||||
| P2P Trade Gone Wrong | 36 |
|
||||
| Armed Robbery in Public Space | 25 |
|
||||
| Costly Fame | 19 |
|
||||
@@ -199,25 +200,25 @@ 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 | 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 |
|
||||
| Repeat victimisation / several incidents on one record | 43 | 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, 493 |
|
||||
| Insider, intimate or acquaintance perpetrator | 42 | 13, 21, 33, 43, 46, 59, 69, 70, 81, 97, 108, 116, 130, 133, 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 | 11 | 133, 139, 144, 190, 318, 354, 355, 412, 419, 423, 457 |
|
||||
| Extortion at a distance or threat at the door without entry | 10 | 139, 144, 190, 318, 354, 355, 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) | 11 | 50, 90, 93, 104, 109, 117, 164, 182, 258, 385, 448 |
|
||||
| Preparation: leaks, surveillance, trackers, data breaches | 18 | 83, 91, 121, 123, 133, 145, 183, 184, 185, 384, 422, 445, 446, 453, 469, 472, 490 |
|
||||
| Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation) | 12 | 50, 90, 93, 104, 109, 117, 164, 182, 258, 385, 448, 492 |
|
||||
| Preparation: leaks, surveillance, trackers, data breaches | 19 | 83, 91, 121, 123, 145, 156, 183, 184, 185, 384, 422, 445, 446, 453, 469, 472, 490, 493 |
|
||||
| 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 |
|
||||
| Security measures deciding the outcome | 8 | 126, 186, 257, 439, 440, 441, 473, 493 |
|
||||
| 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 | 22 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 181, 188, 254, 255, 357, 358, 384, 407, 412, 465, 471, 486, 490 |
|
||||
| Amount and coin fields cannot split crypto from cash, goods or fiat | 24 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 133, 181, 188, 254, 255, 357, 358, 384, 407, 412, 465, 471, 486, 490, 496 |
|
||||
| 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 |
|
||||
| Initiation or entry method not reported | 6 | 141, 223, 409, 454, 477, 485 |
|
||||
| Remote operator, phone drained after the event, or company infrastructure | 4 | 28, 164, 196, 211 |
|
||||
| Other | 416 | 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, 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, 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 |
|
||||
| Other | 434 | 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, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 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, 492, 493, 494, 495, 496 |
|
||||
|
||||
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).
|
||||
|
||||
@@ -265,6 +266,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 472: three attacks by three different teams on one address in a month: the labels carry no notion of repeat victimisation
|
||||
- case 483: a theft spread over repeated routine stops has no single date, which the date field forces
|
||||
- case 487: two victims held in one attack are carried on one record with a single victim field
|
||||
- case 493: repeat victimisation has no field: this is the second attempt on the same household in under six months and the April attack is a separate record (DB record 429)
|
||||
|
||||
### Insider, intimate or acquaintance perpetrator
|
||||
|
||||
@@ -281,6 +283,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 108: the attackers included a former employee who knew the household; insider knowledge is not expressed by any label
|
||||
- case 116: a serving police constable who identified the target from inside the cybercrime cell is insider misuse; Authority Misuse as the glossary defines it needs authority used to gain the victim's compliance, which this report does not describe
|
||||
- case 130: the target was picked because the gym's operator knew his business - an insider at a place the victim used voluntarily, which no label names
|
||||
- case 133: the instigator was the victim's former collaborator pressing a pay dispute: targeting vector = business counterparty / insider
|
||||
- case 139: an attacker who claims a prior acquaintance with the victim, which is what got the conversation started, is not covered
|
||||
- case 152: an insider at a government agency supplying the targeting data has no label
|
||||
- case 153: held at the friends' flat he was invited to: captivity without transport, tagged Kidnapping per the convention
|
||||
@@ -356,7 +359,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
|
||||
### Extortion at a distance or threat at the door without entry
|
||||
|
||||
- case 133: entry gained by a pretext at the door rather than by force has no label; Home Invasion is the closest
|
||||
- case 139: extortion by surrounding a victim in a public cafe, followed by weeks of Telegram demands, has no label; Mugging is the closest public-space label although no assault is described
|
||||
- case 144: the only account of how the attack unfolded is a colleague's Telegram post; the police report is quoted only for time, place and amounts
|
||||
- case 190: the ruse at the door — a stranger claiming to have damaged the garage — is neither a home invasion by force nor a Malicious Invitation
|
||||
@@ -395,6 +397,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 258: the men wore military uniform and posed as recruitment-centre staff while one of those detained really is a serviceman, and no field separates a fake uniform from a real one
|
||||
- case 385: the accusation of being a scammer — the pretext that made the fake arrest plausible — has no field, and neither does the fact that the complaint reached the real police through a third party
|
||||
- case 448: the fake Amazon delivery man used to get the door open has no label of its own
|
||||
- case 492: the law-enforcement legend and the military-pattern uniform are recorded for the group as a whole, at its formation, and are not attributed to the 15 May approach, so Authority Misuse rests on the group's stated method rather than on a described uniform at the scene
|
||||
|
||||
### Preparation: leaks, surveillance, trackers, data breaches
|
||||
|
||||
@@ -402,8 +405,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 91: ten days of surveillance before a street stop with forged credentials is planning that neither label records
|
||||
- case 121: prior reconnaissance of the victim's address is described by the victim but has no label of its own
|
||||
- case 123: the victim describes days of surveillance and a man waiting at the hotel door, which sits badly with Mugging's opportunistic, unplanned character
|
||||
- case 133: weeks of surveillance to establish that the target owned Bitcoin is not expressible in the label set
|
||||
- case 145: the preparation - SIM-swapping victims' exchange accounts, target research over an encrypted app, several trips before the invasion - has no label
|
||||
- case 156: the preparation phase (the couple's email account hacked, days of surveillance) has no label
|
||||
- case 183: the reconnaissance phase ('they learned that the man had Bitcoins ... tracked down where he lived') has no label
|
||||
- case 184: the preparation phase — weeks of physical and digital surveillance, a GPS tracker, forged passports, a recruited hacker — has no label
|
||||
- case 185: an inside leak ('someone close to the victims knew about their financial movements') has no label
|
||||
@@ -416,6 +419,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- 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
|
||||
- case 493: targeting vector: unknown - neither article says how the trio found the address, and Journal du Coin states that no link between the two expeditions has officially been established ("Aucun lien entre les deux expéditions n'a été établi officiellement à ce stade"); Cryptoast's passage on consumer data leaks is general context, not a finding about this family
|
||||
|
||||
### Drugging as the approach
|
||||
|
||||
@@ -448,6 +452,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- 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
|
||||
- case 473: an attempt stopped by the door itself, with no contact and no confrontation, is only loosely served by Dodged Attack, which the glossary frames around victim awareness or security measures
|
||||
- case 493: the perimeter alarm is what ended the attempt, and no field records the defence that worked
|
||||
|
||||
### Scope: fraud, non-violent, or not crypto-linked
|
||||
|
||||
@@ -492,6 +497,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 118: the target was a crypto consultant and the loss was two watches; the labels do not distinguish an attack on a crypto figure whose crypto was never touched
|
||||
- case 123: no cryptocurrency was demanded or taken; the record's own coin_type reads Watch
|
||||
- case 128: nothing crypto was taken - the loss was watches, a ring and cash - so the case sits in this database on the motive alone
|
||||
- case 133: the crypto was defended; the loss was a phone and jewellery, which the coin and amount fields cannot express
|
||||
- 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 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 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
|
||||
@@ -505,6 +511,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- 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
|
||||
- case 496: cryptocurrency and high-value watches were both taken and the record's money fields carry neither
|
||||
|
||||
### Control moves between places; one venue field
|
||||
|
||||
@@ -539,7 +546,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
### Initiation or entry method not reported
|
||||
|
||||
- case 141: how he was lured into the vehicle is not described
|
||||
- case 156: how the two got inside is not reported, so the initiation method has no label
|
||||
- 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 409: no source gives a venue, and Home Invasion, Kidnapping and Armed Robbery all turn on where control was taken, so none of the eleven labels can be supported
|
||||
- case 454: the record's "garage" is not in the file, which says only a room
|
||||
@@ -719,6 +725,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- case 153: a robbery staged by the hosts on themselves, so that the victim reports it as a crime against all of them, has no label
|
||||
- case 154: an attack commissioned and paid for by aggrieved investors has no label
|
||||
- case 154: the killing is the outcome of this case rather than a label of its own
|
||||
- case 156: the transfer was executed remotely by an accomplice who accessed the computer, which no label expresses
|
||||
- case 157: a room prepared for torture that was never used fits no violence category
|
||||
- case 161: an attack directed by telephone from an off-site organiser has no label
|
||||
- case 161: the men arrested are not the three who carried out the attack, who left the country; the record and the label attach to the people in the villa
|
||||
@@ -971,6 +978,23 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
|
||||
- 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
|
||||
- case 492: targeting vector: unknown - the file says the group's targets were people who trade cryptocurrency and that the four addressed him by name and patronymic to show they knew who he was, but it does not say where that knowledge came from
|
||||
- case 492: the loss splits three ways - 170,000 dollars of cryptocurrency, 130,000 dollars of cash collected the same day, and a standing demand for half the business's monthly profit - and the record carries only the crypto
|
||||
- case 492: the organiser is a serving officer using his unit's issue weapons and the record has no field for that
|
||||
- case 492: the same prosecution covers a second victim taken at Kharkiv on 10 October 2025, and there is no field linking records that belong to one organised group
|
||||
- case 493: the crypto motive of the 29 September attempt is inferred by both outlets from the April attack, and no field records a motive carried over from an earlier incident
|
||||
- case 494: targeting vector: unknown - the file says only that the victim "aurait été attirée dans un piège" and does not say who set the trap, how the victim was approached, or how the victim was selected
|
||||
- case 494: the attacker count is not stated anywhere in the file
|
||||
- case 494: the case is at the pre-trial stage and the accused denies the charge, and the record has no field for a contested allegation
|
||||
- case 494: the file does not say where the victim was beaten and tied, so no second label (Home Invasion, Kidnapping or Armed Robbery) can be supported after the lure
|
||||
- case 494: the whole record rests on one 1,444-character item which is itself a summary of a 24 heures article that could not be retrieved
|
||||
- case 495: a home invasion that took full control of the house and still left with nothing sits between Home Invasion and Dodged Attack, and the sequence can only carry one of them
|
||||
- case 495: seven defendants with distinct roles (a ringleader, two lookouts, a car supplier) and the record has no attacker count or role field
|
||||
- case 495: targeting vector: unknown - the district attorney's office says "The house was targeted and the intruders believed the victims had high-value cryptocurrency" and Davis allegedly put the figure at $3.8 million, but no source says where the group got the information
|
||||
- case 495: the only property taken was a phone snatched on the way out and recovered nearby, which the binary theft flag cannot express
|
||||
- case 496: a fourth participant who directed the attack by video call without being in the room has no field; Decrypt reads it against CertiK's account of organisers who buy data and coordinate logistics above the people who carry out the attacks
|
||||
- case 496: a pregnant victim threatened at knifepoint and a husband with significant injuries sit behind one violence flag
|
||||
- case 496: targeting vector: unknown - detectives call it "a planned and targeted attack" and a fourth person directed the three by video call, but no source says how the couple were identified as crypto holders
|
||||
|
||||
## Cases to decide on scope, merge or split
|
||||
|
||||
@@ -978,6 +1002,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, 255, 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, 492]
|
||||
|
||||
Record-only (restructured from the DB record; nothing to verify against): [11, 45, 66, 399]
|
||||
|
||||
Reference in New Issue
Block a user