Archived
docs(verify): consolidated verification report and README update
make_verification_report.py builds batches/VERIFICATION-REPORT.md (coverage, contradictions by field, flag proposals, label frequency, cases no label fits, label gaps by theme, scope/merge/split decisions) and batches/contradictions-ALL.md from the applied batch files. README progress and quick-start rewritten for the finished verification; the old enrichment method is kept for reference. 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
9470e6bb0c
commit
c9d6a0f2fd
+31
-28
@@ -109,7 +109,7 @@ Two different kinds of change came out of this work. They are NOT the same:
|
||||
- verify_all.py PASSES (896 checks). Confirmed from this bundle's new location.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
## The task in progress: summary enrichment
|
||||
## The summary enrichment method (finished 2026-09-30; kept for reference)
|
||||
|
||||
Goal: bring the short/weak bulk-import summaries up to the standard of the newest cases
|
||||
(447-462), which have six labelled categories and run roughly 970-2100 characters:
|
||||
@@ -170,21 +170,24 @@ foiled plots, and any known wrong-source case so it does not over-flag."
|
||||
--------------------------------------------------------------------------------
|
||||
## Progress
|
||||
|
||||
Done and reviewer-verified: batches 1-7, 70 of 256 cases. IDs completed:
|
||||
B1: 372,371,370,369,368,367,365,364,362,353
|
||||
B2: 350,349,340,334,323,322,321,317,315,312
|
||||
B3: 309,308,307,304,303,301,299,298,297,296
|
||||
B4: 293,292,290,288,285,279,273,272,271,270
|
||||
B5: 266,263,256,253,252,249,248,247,246,245
|
||||
B6: 244,243,242,240,238,237,236,235,234,233
|
||||
B7: 232,231,230,229,228,224,222,221,219,218
|
||||
2026-09-30: every case in the export has a verified summary and a scenario sequence, except
|
||||
where noted in merge-output/batches/VERIFICATION-REPORT.md. The 70 cases done by hand
|
||||
(IDs 218-372, batches B1-B7 of the old method) were kept; the remaining 319 were verified in
|
||||
32 batches of ten (merge-output/batches/batch-NN.json) per VERIFICATION-PROCEDURE.md: an
|
||||
opus writer per batch, a read-only sonnet checker per batch, fixes applied, then
|
||||
apply_batch.py. summary-overrides.json and scenario-sequences.json hold one entry per case.
|
||||
verify_all.py PASSES.
|
||||
|
||||
summary-overrides.json holds 70 entries. verify_all.py PASSES.
|
||||
|
||||
Remaining: continue descending from ID 217 (217,216,215,214,213,212,211,210,208,207 ...) down to
|
||||
case 1 - about 186 short cases, roughly 19 more batches. Get the exact remaining list with:
|
||||
python ".../merge-output/survey_summaries.py"
|
||||
and take the ids flagged SHORT / unstructured, descending.
|
||||
Deliverables for Sofia (all proposals; the DB export is untouched):
|
||||
- merge-output/batches/VERIFICATION-REPORT.md: coverage, contradiction counts by field,
|
||||
flag proposals, label frequency, the cases no label fits, label gaps by theme, and the
|
||||
scope/merge/split decisions. Regenerate with make_verification_report.py after any apply.
|
||||
- merge-output/batches/contradictions-ALL.md: every record-vs-article contradiction with the
|
||||
quoted article line, merged from contradictions-01..32.md.
|
||||
- merge-output/batches/flag-proposals.json: every flag the file does not support, with the
|
||||
proposed value and evidence line.
|
||||
- merge-output/exports/gart-kr-database-<date>.xlsx: the review sheet (export_xlsx.py).
|
||||
- merge-output/sofia-worklist.md: manual fetch list, case notes, batch pointers.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
## 2026-09-05 update: linked URLs fetched for the 252 spreadsheet-only cases
|
||||
@@ -253,16 +256,16 @@ file; remove the stale one or verify_all.py reports one file too many.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
## Quick-start checklist for the next AI
|
||||
1. Read this file and merge-output/sofia-worklist.md.
|
||||
2. Confirm the bundle is healthy:
|
||||
python ".../merge-output/verify_all.py" (should say PASS)
|
||||
summary-overrides.json should have 70 entries.
|
||||
3. Pick the next ~10 short cases descending from ID 217 (use survey_summaries.py). Read each
|
||||
dossier in full. Write build_overrides_batch8.py (copy batch 7's structure). Run it, then
|
||||
build_cases.py --all, then verify_all.py.
|
||||
4. Run the source-checker agent on the batch (read-only, no fetch). Apply fair flags; rebuild;
|
||||
verify. Then the batch is locked.
|
||||
5. Repeat down to case 1.
|
||||
6. Keep adding DB field/source problems to sofia-worklist.md. Never edit the DB.
|
||||
7. When all summaries are done, the deliverables are: the sources/*.txt (already carry the
|
||||
improved summaries) and sofia-worklist.md (Sofia's manual DB fixes, done last on her side).
|
||||
1. Read this file, merge-output/DEFINITIONS.md and merge-output/VERIFICATION-PROCEDURE.md.
|
||||
2. Confirm the bundle is healthy: python merge-output/verify_all.py (should say PASS);
|
||||
summary-overrides.json and scenario-sequences.json should have one entry per DB case.
|
||||
3. New cases: python merge-output/pull_live_cases.py, then fetch (stage_all.py
|
||||
--include-sheet-cases, wayback_pass.py, auto_trim.py), build_cases.py --all, verify_all.py.
|
||||
Then verify them as a new batch: add the ids to batches/batch-lists.json, run a writer
|
||||
agent with batches/WRITER-PROMPT.md, a read-only checker, batches/validate.py,
|
||||
apply_batch.py, make_verification_report.py, export_xlsx.py.
|
||||
4. Never edit the DB export or the xlsx sheet by hand. Every correction is a proposal in
|
||||
batches/ or sofia-worklist.md until Sofia applies it.
|
||||
5. Commit on branch fetch-sheet-only-sources with the StellarCrow identity; main holds only
|
||||
the handoff bundle and DEFINITIONS.md. Gitea pushes may print "Terminated" but land:
|
||||
confirm with git ls-remote --heads origin fetch-sheet-only-sources.
|
||||
|
||||
@@ -0,0 +1,929 @@
|
||||
# Verification report — all batches (2026-09-30)
|
||||
|
||||
Every summary, scenario sequence, flag proposal and contradiction below was written from the case's own dossier (sources/<id>_*.txt) by a writer agent and checked line by line by a read-only checker. The DB export is untouched: everything here is a proposal for Sofia. Per-batch detail sits in contradictions-NN.md; the merged list is contradictions-ALL.md.
|
||||
|
||||
## Coverage
|
||||
|
||||
| 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] |
|
||||
| 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.
|
||||
|
||||
| Field | Contradictions |
|
||||
|---|---|
|
||||
| description | 149 |
|
||||
| date | 140 |
|
||||
| amount | 91 |
|
||||
| victim | 78 |
|
||||
| location | 77 |
|
||||
| attackers | 73 |
|
||||
| money_wanted | 44 |
|
||||
| weapons | 41 |
|
||||
| notes | 38 |
|
||||
| detention | 36 |
|
||||
| scenario | 35 |
|
||||
| arrests | 34 |
|
||||
| violence | 32 |
|
||||
| theft | 28 |
|
||||
| coin_type | 17 |
|
||||
| status | 11 |
|
||||
| site summary | 8 |
|
||||
| flags | 7 |
|
||||
| drugs_alcohol | 6 |
|
||||
| victims | 1 |
|
||||
| location of the abduction | 1 |
|
||||
| location of arrest | 1 |
|
||||
| date of arrest | 1 |
|
||||
| description of the first approach | 1 |
|
||||
| life_taken | 1 |
|
||||
| date of announcement | 1 |
|
||||
|
||||
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 12 (Rocelo Lopes' wife): 7
|
||||
- case 433 (Crypto Forum Moderator): 7
|
||||
- case 412 (Mainland Chinese businessman, 25): 7
|
||||
- case 411 (Igor Komarov): 7
|
||||
- case 408 (Yong Wang, Chinese businessman ): 7
|
||||
- case 199 (Igor Lermakov): 6
|
||||
- case 32 (Shailesh Bhatt): 6
|
||||
- case 23 (T.W. (Troy Woody Jr.)): 6
|
||||
- case 459 (Stephanie Mau-Asum and Astrid Robinson ): 6
|
||||
- case 444 (25-year-old wife of a crypto investor): 6
|
||||
- case 434 (Young Pakistani male): 6
|
||||
- case 428 (Mother and son (~10 years old)): 6
|
||||
- case 409 (NFT collector and crypto trader "Sillytuna"): 6
|
||||
- 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
|
||||
- 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.
|
||||
|
||||
| Flag | Record | Proposed | Count |
|
||||
|---|---|---|---|
|
||||
| drugs_alcohol | null | 0 | 81 |
|
||||
| drugs_alcohol | 1 | unconfirmed | 4 |
|
||||
| drugs_alcohol | 0 | unverified | 4 |
|
||||
| drugs_alcohol | 0 | 1 | 2 |
|
||||
| drugs_alcohol | 1 | 0 | 2 |
|
||||
| kidnappings | 0 | 1 | 40 |
|
||||
| kidnappings | 1 | 0 | 6 |
|
||||
| kidnappings | 1 | unconfirmed | 4 |
|
||||
| kidnappings | null | 0 | 3 |
|
||||
| kidnappings | 0 | unverified | 3 |
|
||||
| kidnappings | 0 | unconfirmed | 1 |
|
||||
| kidnappings | 1 | unverified | 1 |
|
||||
| life_taken | 0 | unverified | 4 |
|
||||
| life_taken | null | unconfirmed | 3 |
|
||||
| life_taken | null | 0 | 2 |
|
||||
| life_taken | 0 | 1 | 1 |
|
||||
| life_taken | 1 | unconfirmed | 1 |
|
||||
| theft | 0 | 1 | 15 |
|
||||
| theft | 1 | unconfirmed | 14 |
|
||||
| theft | null | unconfirmed | 9 |
|
||||
| theft | 1 | 0 | 4 |
|
||||
| theft | null | 0 | 4 |
|
||||
| theft | 1 | unverified | 3 |
|
||||
| theft | 0 | unverified | 1 |
|
||||
| theft | null | 1 | 1 |
|
||||
| violence_torture | 0 | 1 | 23 |
|
||||
| violence_torture | null | 0 | 16 |
|
||||
| violence_torture | 1 | threat only | 6 |
|
||||
| violence_torture | 1 | 0 | 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 | null | 0 | 31 |
|
||||
| weapons | 0 | 1 | 30 |
|
||||
| weapons | 1 | unconfirmed | 20 |
|
||||
| weapons | 1 | 0 | 12 |
|
||||
| weapons | null | 1 | 9 |
|
||||
| weapons | null | unconfirmed | 8 |
|
||||
| weapons | 0 | unverified | 2 |
|
||||
| weapons | 1 | unverified | 2 |
|
||||
| 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 1 → 0 (6): [124, 128, 151, 195, 406, 423]
|
||||
|
||||
Fatality flag (life_taken) proposals:
|
||||
|
||||
- case 355: null → 0 — no death
|
||||
- case 354: null → 0 — no death
|
||||
- case 45: 0 → unverified — no source on file describes the incident
|
||||
- case 485: null → unconfirmed — "No body has been recovered. No confirmed sighting has surfaced"; crypto.news says "no publicly cited court judgment has established that he is dead"
|
||||
- case 12: 0 → 1 — "Armed police officers descended on the location and were able to free the hostage and arrest many of the conspirators, killing one in the process" (Business Insider); the Brazilian accounts report one arrest and no death
|
||||
- case 11: 0 → unverified — no article on file; the record is the only statement
|
||||
- case 443: null → unconfirmed — possible foul play is suspected but there is no body and no death is reported; he was still missing as of the latest article
|
||||
- case 467: null → unconfirmed — both men remain missing and no body is reported; the two dead men in the same article are the June 2024 medical executives, a separate case
|
||||
- case 66: 0 → unverified — no article on file; the record is the only statement
|
||||
- case 399: 0 → unverified — no article or statement on file; the record is the only text
|
||||
- case 411: 1 → unconfirmed — 'Police have not yet confirmed that the body belongs to Komarov and are conducting DNA testing' (Pravda); the coroner said identification was impossible due to advanced decomposition and police had only a partial tattoo match
|
||||
|
||||
## Scenario sequences
|
||||
|
||||
| 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 no label fits (empty sequence) | 23 |
|
||||
|
||||
Label frequency across all sequences:
|
||||
|
||||
| Label | Uses |
|
||||
|---|---|
|
||||
| Kidnapping | 127 |
|
||||
| Home Invasion | 103 |
|
||||
| Malicious Invitation - SocialEng | 66 |
|
||||
| Dodged Attack | 53 |
|
||||
| P2P Trade Gone Wrong | 36 |
|
||||
| Authority Misuse | 33 |
|
||||
| Armed Robbery in Public Space | 26 |
|
||||
| Costly Fame | 19 |
|
||||
| Express Kidnapping | 17 |
|
||||
| Assault - Mugging | 8 |
|
||||
| Swatting | 2 |
|
||||
|
||||
Cases no label fits, with the writer's reason:
|
||||
|
||||
- case 3 (Martin Wismeijer): Both incidents are forced-entry thefts of hardware from closed businesses — no weapon, no confrontation, nobody present — so Armed Robbery in Public Space fails on both "armed" and the presence of anyone to rob, and no other label in the glossary fits.
|
||||
- case 6 (Robert Nederhoed): The machine was torn from its anchors and carried out of the café during the night with nobody present and no weapon, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 10 (Tivoli Brasserie): The machine was lifted and carried out with nobody present and no weapon, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 11 (Josoj): Record-only: the sole linked source is a podcast reference with no article text, so no label can be tested against anything — marked unsupported for lack of evidence, not because P2P Trade Gone Wrong looks wrong.
|
||||
- case 21 (Unidentified): The record's Armed Robbery in Public Space is contradicted by the file: no weapon, no victim present, no confrontation and no public space, but a planned night entry into a data centre using a recruited guard's codes.
|
||||
- case 24 ("Dallas"): The record's Armed Robbery in Public Space is not in the file: nothing was stolen or demanded, the accused was the buyer who wanted the sale called off, and the shot was fired inside a private condo during an argument.
|
||||
- case 45 (Austin Nedved): Nothing on file describes any incident on 6 July 2018, so no label can be supported: the Swatting scenario, the armed home invasion in the description and the date itself all rest on material that is not in this file.
|
||||
- case 57 (Simply Delicious Food Market): Two masked men broke into a closed grocery store at about 4 a.m. and took the cash out of the bitcoin ATM; nobody was present and no weapon is reported, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 62 (Mayfair Quick Mart): Two men pried the store's Bitcoin machine open with crowbars and took the cash box in seconds; nobody was threatened and no weapon was used against a person, so the record's Armed Robbery in Public Space is not supported — the same problem as 101, 105 and 198.
|
||||
- case 66 (Exxon Gas Station): Nothing on file supports Armed Robbery in Public Space: the record itself describes a machine pried open, with no weapon, no threat and no person held, and there is no article against which the label could be tested.
|
||||
- case 99 (Mark Geor): A burglary of an unoccupied house under renovation: nobody was present, nobody was confronted and no weapon was used against a person, so the record's Armed Robbery in Public Space label is not supported and none of the eleven labels fits.
|
||||
- case 101 (Liquor Store): An overnight break-in at a closed store to drag an unattended Bitcoin ATM out through the front with a van; nobody was present and nobody was threatened, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 105 (GBTC Crypto Exchange): A 3 a.m. ram raid on a shuttered shop and theft of the machine itself; no staff were present and nobody was threatened for access, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 112 (Gas Station): A truck was reversed through the doors of a closed convenience store overnight and the bitcoin ATM carried out; nobody was present and nobody was threatened, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 195 (Gen Z Quant kid): Doxing and an alleged theft of the family dog after a rug pull; no person was held or attacked, so the record's Kidnapping label is not supported and none of the eleven labels fits.
|
||||
- case 198 (Coinflip ATM): Overnight ram raid on a closed shopping centre and theft of the machine itself; nobody was present and no one was threatened, so the record's Armed Robbery in Public Space label is not supported.
|
||||
- case 349 (Unidentified 31 y/o): Overnight burglary of an unoccupied mining garage; no weapon, no one present. None of the eleven labels fits; the record's Armed Robbery label is not supported.
|
||||
- case 383 (Undisclosed): Home Invasion requires occupants held on site, and no person appears in the account at all: the only conduct described is an unlawful entry and the theft of a device, coordinated by tracking the victim's location in real time, with nobody confronted, restraine
|
||||
- case 399 (Young trader): Record-only: no article, no linked source and no statement text on file, so the Malicious Invitation label cannot be tested against anything - marked unsupported for lack of evidence, not because the label looks wrong (it is the most plausible reading of the r
|
||||
- case 409 (NFT collector and crypto trader "Sillytuna"): Home Invasion needs the victim's own private space and no source in this file gives any location at all — not the Hoxton-style address the record carries, not a country; what the file supports is an armed, violent coercion of a $24 million transfer on the vict
|
||||
- case 449 (Unidentified): The DOJ account is a break-in and a hardware-wallet theft with no occupant, confrontation or holding, so Home Invasion by the glossary's definition does not hold (as in 99 and 450) — BleepingComputer's phrase "home invader" is a characterisation of Ferro's rol
|
||||
- case 450 (Undisclosed): Nobody was home by design — the co-conspirators waited for the iCloud signal that the victim had left — so the record's Home Invasion label does not hold (the same problem as 99), and no other label fits a burglary of empty premises.
|
||||
- case 468 (Harry Chun Tak Yeh): No article on file describes an intruder, a confrontation or anyone being held; police were running accident, suicide and homicide in parallel and had not determined how Yeh fell, so the record's Home Invasion label is not supported and none of the eleven labe
|
||||
|
||||
## Label gaps (what the eleven scenarios cannot express)
|
||||
|
||||
Gap notes grouped by theme. Counts are notes, not cases; a case can raise several.
|
||||
|
||||
| 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 |
|
||||
| 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 |
|
||||
| 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 |
|
||||
| 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 |
|
||||
|
||||
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).
|
||||
|
||||
### Repeat victimisation / several incidents on one record
|
||||
|
||||
- case 9: one record stands for a string of robberies with different victims on different dates; there is no way to express a series
|
||||
- case 18: five or six separate robberies over five months sit in one record; there is no way to mark a series
|
||||
- case 32: one record carries what the file describes as two detentions on the same day, at the CBI office and then at the farmhouse, with a release in between
|
||||
- case 38: one record carries two robberies six days apart at two businesses in two cities; there is no field for a series
|
||||
- case 49: two incidents, three months apart and with different victims, sit on one record; the labels, the flags and the date field can each describe only one of them
|
||||
- case 72: one record under one label carries a plot against two intended victims
|
||||
- case 106: a months-long campaign of repeated attempts against one victim cannot be expressed in a single case row
|
||||
- case 134: the attackers' return to the victim's locality to collect more money is a second approach the single record cannot hold
|
||||
- case 162: repeat victimisation across a months-long campaign has no label
|
||||
- case 169: repeat victimisation across a months-long campaign has no label; this is the fifth of five records for one victim
|
||||
- case 169: the shared article reports the campaign's violence collectively, so the machetes, the pistol, the morphine and the cupboard cannot be pinned to individual incidents
|
||||
- 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 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
|
||||
- case 357: five victims sit on one record and only one of them was made to make the transfer
|
||||
- case 374: a repeat campaign against one victim, with several failed attempts before this one, has no label
|
||||
- case 395: the campaign that followed - the forced lock, the petrol poured on the door, the Snapchat threats against the mother and sister - has no label, and the person held is not the crypto holder
|
||||
- case 423: the repeated fake deliveries before and after the attack — four approaches in two hours, and another coffee eight days later — are reconnaissance the labels cannot express
|
||||
- case 436: the group's planned armed reprisal against a Nimes business a week later is a second crime carried on the same record
|
||||
- case 439: the repeat targeting of the same household four times in about six weeks has no label
|
||||
- case 439: three attempts on three consecutive days are held as three separate records, but the only source describes them as one series without dates or order
|
||||
- case 440: the repeat targeting of the same household four times in about six weeks has no label
|
||||
- case 440: three attempts on three consecutive days are held as three separate records, but the only source describes them as one series without dates or order
|
||||
- case 441: the repeat targeting of the same household four times in about six weeks has no label
|
||||
- case 441: three attempts on three consecutive days are held as three separate records, but the only source describes them as one series without dates or order
|
||||
- case 446: the same victim attacked on two consecutive days is split across records 445 and 446, while the sources describe one operation spanning 10-11 May and give no separate account of the second approach
|
||||
- case 463: two victims on one record
|
||||
- case 466: two victims on one record: life_taken carries the 2 but nothing else distinguishes them, and only one family paid
|
||||
- case 467: two victims on one record, with different family decisions on paying
|
||||
- case 470: three attacks by three different teams on one address inside a month, with no label for repeat victimisation
|
||||
- case 471: three teams at one address inside a month: nothing in the labels expresses repeat victimisation of a wrong target
|
||||
- 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
|
||||
|
||||
### Insider, intimate or acquaintance perpetrator
|
||||
|
||||
- case 13: recruiting the victim's own driver as an informant, over weeks, has no label
|
||||
- case 21: the insider recruitment of a security guard, the method that made the theft possible, has no label and no flag
|
||||
- case 33: the friend who came with Tai was assaulted too, and the schema has one victim field
|
||||
- case 43: insiders attacking their own chief executive — the company's marketing team — has no label
|
||||
- case 46: four friends who walk a drunk man into his own flat and then rob him fit no label: entry was not forced and there was no lure to a place of the attackers' choosing
|
||||
- case 59: the operation was set up by a tip-off from the victim's own close friend about the balance in his wallet; betrayal by an insider has no label
|
||||
- case 69: a betrayal by a new acquaintance who brings the attackers to the victim's own room sits between Malicious Invitation and Home Invasion, and the single-scenario rule forces a choice
|
||||
- case 70: the ransom was paid by a relative from her own wallet; the record has no field for who paid
|
||||
- case 81: insider facilitation — reception staff paid and two security guards bribed — has no label
|
||||
- case 97: an intimate partner as one of the plotters has no label; Malicious Invitation carries the betrayal of trust
|
||||
- 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 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
|
||||
- case 170: the ransom was demanded in rubles from a relative, not in crypto from the victim; money_wanted and coin_type have nothing to hold a fiat ransom in a crypto case
|
||||
- case 179: the insider angle — one of the attackers was the victim's friend — has no label
|
||||
- case 186: a transfer executed by the victim's relatives in another country, at the attackers' order, has no label
|
||||
- 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 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
|
||||
- case 386: the whole case rests on one relative's account of what an anonymous friend told him, with no police report and no independent confirmation, and no field records that standard of evidence
|
||||
- case 391: one of the four already had access to the unit and opened the door for the rest; insider access of that kind has no label and no flag
|
||||
- case 396: the man held is not the crypto holder - the ransom was aimed at his son's wallet abroad - and the labels describe the holder, not the relative used as leverage
|
||||
- case 407: insider betrayal — a gang built out of the victim's own trusted staff and their relatives — has no label
|
||||
- case 444: extortion aimed at a third party — a wealthy friend, not the person held — is not expressible
|
||||
- case 447: a relative of the crypto holder targeted in his place has no label
|
||||
- case 448: a ransom extorted from a relative rather than from the person held is not expressible
|
||||
- case 451: extortion aimed at a relative — the ransom was demanded from her son, not from the person held — is not expressible
|
||||
- case 454: the 14,000 euros came from the victim's partner and a friend rather than from his own holdings, so the loss falls partly outside the named victim with no field to say so
|
||||
- case 455: he was held in turn at the friend's house, in scrubland, in a motel and in the boot of a car, which one venue field cannot hold
|
||||
- case 455: the lure came from a twenty-year friend, not a stranger's pretext, which the label does not distinguish
|
||||
- case 457: a household targeted for holdings a relative sold more than a year earlier has no field
|
||||
- case 458: the two women held were not the holder; the relative whose gains were the target has no field
|
||||
- case 475: the victim was befriended in a bar and then made to take his attackers to his own home; no label covers a lure that runs in that direction
|
||||
- case 486: a two-month acquaintance formed at a nightclub and then used as the approach cannot be distinguished from a cold ambush; the report does not say the December meeting was arranged as a trap
|
||||
|
||||
### Empty premises, unattended machines, infrastructure
|
||||
|
||||
- case 2: the reconnaissance a week earlier — two men asking questions about the ATM, then a wallet stolen from the office — is a separate incident the record cannot carry
|
||||
- case 2: the target was a machine rather than a person or their keys, and no crypto was reachable; the label set assumes a human holder
|
||||
- case 2: the victim field holds an employee's name while the loss fell on the shop and the machine's owner
|
||||
- case 3: the eleven labels have no entry for a burglary of unattended commercial premises: no victim was present, no weapon appeared and nothing was extorted from anyone
|
||||
- case 3: the loss fell on the venues and on individual traders whose fiat was inside the machines, which the single victim field cannot show
|
||||
- case 6: a night-time break-in to take an unattended crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it (compare 10, 62, 101, 105, 112, 198)
|
||||
- case 6: the loss is 2,000 euros of banknotes out of a crypto machine, not cryptocurrency, and the theft flag cannot say which
|
||||
- case 10: theft of an unattended crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it (compare 6, 62, 101, 105, 112, 198)
|
||||
- case 10: what was lost is the machine and whatever cash sat in it, not cryptocurrency, which the record's coin_type of "bitcoin" misstates
|
||||
- case 11: the record's own description — a robbery during a Localbitcoins trade — reads as P2P Trade Gone Wrong, but with no report on file no label can be tested, so none is asserted (same treatment as 45 and 66)
|
||||
- case 19: the burglary of the victim's empty apartment, running at the same time as the detention in the van, has no label of its own
|
||||
- case 21: a stealth burglary of a mining facility with nobody present fits none of the eleven labels, which all describe attacks on people
|
||||
- case 38: the target was the cash inside a Bitcoin ATM and the victims were shop clerks, which no label distinguishes from an attack on a crypto holder
|
||||
- case 51: a weapon used to hold staff off while a machine is ripped from the wall sits between Armed Robbery and a straight burglary
|
||||
- case 51: the target was the shop's Bitcoin machine rather than a holder's wallet, and the people threatened were shop staff with no stake in any cryptocurrency - an attack on crypto infrastructure has no label
|
||||
- case 54: a smash-and-grab raid on unattended commercial premises has no label; the record files it under Armed Robbery in Public Space although no weapon and no confrontation is reported (compare 158)
|
||||
- case 54: the machine and its cash float, not a holder's wallet, were the target - an attack on crypto infrastructure has no label
|
||||
- case 57: an overnight break-in at a closed shop to empty a crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it (compare 198, 112 and 158)
|
||||
- case 57: the target was crypto infrastructure and its cash float, not a holder's wallet
|
||||
- case 62: a smash-and-grab of a crypto ATM's cash box, with staff present but never confronted, has no label; the eleven scenarios all assume a person is threatened
|
||||
- case 62: the loss is fiat cash out of a crypto machine, not cryptocurrency, which is why coin_type has to read "Bitcoin ATM'S Cash"
|
||||
- case 66: a smash-and-grab of a crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it
|
||||
- case 71: the machine, not a holder, was the target — an attack on crypto infrastructure has no label
|
||||
- case 84: the attempt was on mining hardware in the yard of a private house, which neither Dodged Attack nor Armed Robbery locates
|
||||
- case 85: the ATM withdrawal by a man unknown to the victim unknown to the victim, a stage after the invasion, has no field
|
||||
- case 101: theft of an unattended crypto ATM has no label; the eleven scenarios all assume a person is present to be threatened
|
||||
- case 102: the label says "in Public Space"; the scene was a mining operation in a village, and the glossary's Armed Robbery entry is what actually covers mining facilities
|
||||
- case 105: a ram-raid theft of a crypto ATM from a closed shop has no label; none of the eleven scenarios covers a crime with no person in it
|
||||
- case 112: a ram-raid theft of an unattended crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it (compare 198 and 158)
|
||||
- case 112: the target was crypto infrastructure rather than a holder
|
||||
- case 158: a ram-raid burglary of unoccupied commercial premises has no label; the record files it under Armed Robbery in Public Space although no weapon and no confrontation is reported
|
||||
- case 158: the machine, not a holder, was the target — an attack on crypto infrastructure has no label
|
||||
- case 198: a ram-raid theft of an unattended crypto ATM has no label; none of the eleven scenarios covers a crime with no person in it
|
||||
- case 352: the label reads "in Public Space" while the glossary's Armed Robbery entry is the one that actually covers mining facilities
|
||||
- case 352: the record's Home Invasion label has nothing to rest on: the site was a mining farm under construction, not a residence, and nobody was held
|
||||
- case 383: the cyber intrusion, the purchased user data and the real-time iCloud tracking that made the burglary possible are the method of this case and have no field
|
||||
- case 389: the several attempted burglaries against the same family over the Christmas holidays are part of the same targeting and have no field
|
||||
- case 399: the record's own description - lured to an apartment for a cash trade and ambushed there - reads as Malicious Invitation plus captivity at the attackers' premises, but with nothing on file to test it no label is asserted (same treatment as 11, 45 and 66)
|
||||
- case 420: the labels do not record that the intended target (crypto keys) yielded nothing while a conventional burglary of cash, silver and jewellery succeeded
|
||||
- case 449: a burglary in which no occupant appears fits none of the eleven labels; Home Invasion in the glossary requires occupants held on site
|
||||
- case 450: a burglary deliberately timed for an empty house fits none of the eleven labels; Home Invasion in the glossary requires occupants held on site
|
||||
|
||||
### Extortion at a distance or threat at the door without entry
|
||||
|
||||
- case 44: a ruse at the door — men posing as parcel couriers — has no label; the deception got them inside rather than luring the victim out
|
||||
- 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
|
||||
- case 318: the probe at the door and the armed confrontation days later are split across two records (this one and 433), so the handgun, the spray and the torture kit cannot be counted here
|
||||
- case 354: extortion by threat at the door, without entry or holding, has no label; tagged Home Invasion as the closest
|
||||
- case 355: a weapon threat at the door to extort, without entry, sits uneasily under Home Invasion
|
||||
- case 403: a delivery-driver ruse at the door has no label: it opened the door rather than luring the victim anywhere, and Authority Misuse needs a position of power a courier does not carry
|
||||
- case 412: police classified the case as blackmail and false imprisonment, which none of the eleven labels renders
|
||||
- case 419: the file stops at the doorstep, so the labels cannot say whether the attackers ever got inside — the difference between Dodged Attack and Home Invasion here
|
||||
- case 423: an attack broken by the victim's own physical resistance at the door has no label distinct from the rest of Dodged Attack
|
||||
- case 457: attack size is unrecorded because no source says how many people were at the door
|
||||
|
||||
### Lured to and held at the attackers' venue (captivity without transport)
|
||||
|
||||
- case 15: being held for hours at a third-party venue without being moved has no label; the file's convention makes a victim lured to and held at the attackers' premises a Kidnapping, but nothing says the club was theirs
|
||||
- case 53: the file's convention treats a victim lured to and held at the attackers' premises as Kidnapping; here the lure was an offer to sell bitcoin cheaply and the flat was the gang's, so the initiation reads as a fake trade and the captivity as a kidnapping, which the single-category rule cannot hold together
|
||||
- case 60: the lure and the captivity happened at premises the attacker rented for the purpose, which the labels treat as a kidnapping venue although the victim walked in voluntarily (the file's convention: lured to and held at the attackers' premises = Kidnapping)
|
||||
- case 110: the victims were forced into the attackers' cells inside the same institution rather than transported anywhere, so Kidnapping holds only in the sense the charge sheet uses it (compare the convention for a victim held at the attackers' premises)
|
||||
- case 157: held at the attackers' villa after days of socialising with them: captivity without transport, tagged Kidnapping per the convention
|
||||
- case 162: held overnight at the attackers' flat after going to the address himself: captivity without transport, tagged Kidnapping per the convention
|
||||
- case 181: the victim was lured to and held at the attackers' apartment rather than taken from his own space; Kidnapping is applied under the standing convention for that pattern
|
||||
- case 200: the 19 December victim was held at the attackers' office and never moved; tagged Kidnapping under the convention for captivity at the attackers' premises
|
||||
- case 213: held at the attackers' rented apartment after accepting an invitation: captivity without transport, tagged Kidnapping
|
||||
- case 461: the file does not say what the victims did, so whether the attempt failed through their response or the attackers' own choice is unrecorded
|
||||
|
||||
### Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation)
|
||||
|
||||
- case 50: the police disguise is the entry method and the raid is the attack; the single-scenario rule forces a choice between them
|
||||
- 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 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
|
||||
- case 182: the pretext was a professional enquiry about a course rather than an invitation to an event, which the Malicious Invitation label covers only loosely
|
||||
- case 184: a disguise-based ambush at the victim's own door is not a Malicious Invitation: nothing lured him anywhere
|
||||
- case 185: the police uniforms on the footage and the OIJ's belief that the attackers had police training point at Authority Misuse, but the report does not say they presented themselves as officers or that the victims complied on that basis, so the label is not applied
|
||||
- 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 360: a courier ruse used to get a door opened has no label: Malicious Invitation covers luring a victim out, not deceiving him at his own threshold
|
||||
- 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 402: posing as a delivery driver to get the door opened is a ruse, not a claim of authority; none of the eleven labels covers entry by impersonation of a private company
|
||||
- case 413: the postal-carrier disguise is a delivery ruse, which the glossary has no label for
|
||||
- case 429: a fake-delivery ruse used to get through the door has no label of its own
|
||||
- case 438: a doorstep parcel-delivery ruse has no label; the deception opened the door rather than luring the victim out
|
||||
- case 442: a doorstep ruse — a fake food delivery — has no label; the deception opened the door rather than luring the victim out
|
||||
- case 444: the fake-delivery ruse that got the door open has no label of its own
|
||||
- case 447: the fake-delivery ruse that got the gate opened is not expressible
|
||||
- case 448: the fake Amazon delivery man used to get the door open has no label of its own
|
||||
- case 451: the fake-delivery ruse that got the door open has no label of its own
|
||||
- case 479: the food-delivery ruse that got the door open has no label; the deception brought the attackers in rather than luring the victim out
|
||||
|
||||
### Preparation: leaks, surveillance, trackers, data breaches
|
||||
|
||||
- case 83: the report does not say whether the robbers were the people he had arranged to sell to or a third party who knew about the meeting, so the label rests on the arranged sale plus the word 'deception'
|
||||
- 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 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
|
||||
- case 384: the 15 arrests point to a syndicate with surveillance, drivers and handlers behind three men on the pavement, and the record has no way to show roles
|
||||
- case 422: the file never states what the attacker intended to demand once inside the garage, only that the victim believed his crypto holdings had been leaked
|
||||
- case 422: the reconnaissance pattern the victim described (unordered food deliveries, a free driveway-cleaning offer) has no label
|
||||
- case 445: targeting built on a data leak about the victim's crypto transactions has no label of its own
|
||||
- case 446: targeting built on a data leak about the victim's crypto transactions has no label of its own
|
||||
- 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
|
||||
|
||||
### Drugging as the approach
|
||||
|
||||
- case 48: he was drugged unconscious at one address and woke at another, so the record's single location field cannot hold both the lure address and the place of captivity
|
||||
- case 88: a chat-app lure that ends in a spiked drink and a fingerprint pressed to a sensor is Malicious Invitation, but the label says nothing about the drugging being the whole means of access
|
||||
- case 92: a dating-app lure that ends in drugging at the victim's own home, with no detention and no weapon, is Malicious Invitation but the label says nothing about the drugging being the whole means of coercion
|
||||
- case 97: the file never describes a period of captivity or how the victim got from the couple's house in Plancher-les-Mines to the pond in Plancher-Bas, so Kidnapping rests on the lure plus the alleged drugging and the body's location
|
||||
|
||||
### Unexplained death or undetermined circumstances
|
||||
|
||||
- case 26: the impersonation of Interpol is the entry method and the holding is the operation; the single-scenario rule makes one of the two disappear
|
||||
- case 58: a disappearance with a ransom note and a Monero demand but no proof of captivity, which police later thought might be a staged kidnapping, fits no label; Kidnapping records the police's first theory rather than an established fact
|
||||
- case 58: the labels cannot express a case where the crime itself is undetermined
|
||||
- case 207: no ransom demand is reported, so what the three days of captivity were for is unexplained
|
||||
- case 295: a death with undetermined circumstances has no label; the record files it under the earlier alleged kidnapping
|
||||
- case 392: where the couple were held between the abduction and Montélimar is never stated, so one label has to carry two days of unexplained captivity
|
||||
- case 400: a disappearance that police treat as an abduction, with no suspect, no holding place and no confirmed motive, fits Kidnapping only as police belief, not as an established sequence
|
||||
- case 443: an unresolved disappearance in which no abduction has been established fits no label cleanly; the Kidnapping label here records a police hypothesis, not an observed event
|
||||
- case 467: both men are still missing: none of the six outcome values covers an unresolved disappearance
|
||||
- case 468: an unexplained death of a crypto holder, with a ransacked flat and no established intruder, fits none of the eleven labels
|
||||
- case 468: the file cannot say whether a crime occurred at all, and the schema has no undetermined state
|
||||
- case 485: an unresolved disappearance that is only reported as a kidnapping has no label for an unestablished attack; nothing in the file confirms he was taken, only that his family received messages saying so
|
||||
|
||||
### Security measures deciding the outcome
|
||||
|
||||
- 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 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
|
||||
- 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
|
||||
|
||||
### Scope: fraud, non-violent, or not crypto-linked
|
||||
|
||||
- case 8: what was taken is the cash side of the trade, not crypto, which money_wanted of "$28,000" hides
|
||||
- case 18: one of the counts involved no meeting at all, a money transfer with no bitcoin delivered, which is fraud rather than a physical attack
|
||||
- case 27: the loss was the cash brought to buy crypto with, not crypto; the labels and amount fields do not distinguish the two
|
||||
- case 39: the loss was the cash carried to buy crypto with, not crypto; the labels and amount fields do not distinguish the two
|
||||
- case 42: a fraud that turns violent only once the victim spots it sits between the trade label and robbery; what was actually stolen was the cash he had earned in the earlier, genuine trade
|
||||
- case 56: the victim is himself an alleged fraudster and the attackers are his own business associates recovering money they say he stole; the labels have no place for a crime inside a criminal enterprise
|
||||
- case 61: the record has no field for the fact that the only account of the ordeal is the victim's own, and that he was himself facing fraud charges at the time
|
||||
- case 73: the file implies a set-up — a "fraudulent bitcoin transaction", a below-market offer and a seller who never arrived — but never links the man who kept them waiting to the four, so Malicious Invitation cannot be added
|
||||
- case 83: the loss was the cash brought to buy crypto with, not crypto; the labels do not distinguish the two
|
||||
- case 89: the loss was the cash he was carrying to buy bitcoin, not crypto; the labels do not distinguish the two
|
||||
- case 94: the loss is fiat cash carried to a crypto trade, not cryptocurrency; the schema's coin and amount fields do not distinguish the two
|
||||
- case 137: what was at stake was the victim's cash, which he was carrying to buy Bitcoin, not crypto he already held; the scenario labels do not distinguish the two sides of a P2P trade
|
||||
- case 150: the attackers' claim that the victim had defrauded someone - a debt-collection motive - has no label
|
||||
- case 260: what was lost is a passport and a ring, not cryptocurrency, which the coin and amount fields cannot express
|
||||
- case 394: a punitive abduction to recover money lost in a crypto fraud has no label, and Express Kidnapping presumes funds are extracted during the detention, which neither article reports here
|
||||
- case 398: the attacker is a defrauded investor recovering his losses by abduction; none of the eleven labels marks that motive, and the same operation is split across two records (397 and this one)
|
||||
|
||||
### Other
|
||||
|
||||
- case 1: a year of remote extortion and threatening phone calls, before and after the hoax call, has no label; only the single swatting event is expressible
|
||||
- case 1: nothing records that the armed response was carried out by police acting in good faith on a false report
|
||||
- case 1: the caller is reported to have extorted several other bitcoin holders, and the serial pattern cannot be linked across records
|
||||
- case 1: the victim's medical condition — what made a half hour on the lawn dangerous — has nowhere to go
|
||||
- case 3: the record carries two separate thefts, at two venues, weeks apart, as one case with one date
|
||||
- case 4: a single robbery standing in for what the victim describes as a pattern among in-person traders has no field
|
||||
- case 4: money_wanted cannot show that only $8,500 of the $12,000 was cryptocurrency and $3,500 was cash
|
||||
- case 4: the dealer was reached through his own advertised service — a caller who had heard about him online or through a referral — which no field records
|
||||
- case 5: a trade the victim himself advertised (a Craigslist ad offering bitcoins for sale) has no field
|
||||
- case 5: control shifted from a street corner to the buyer's car, which a single label cannot show
|
||||
- case 5: the record merges two incidents the article keeps apart — the 27 May bitcoin robbery and a 9 February stabbing police say was not bitcoin related — and no field can carry two events
|
||||
- case 7: an overnight detention conducted entirely inside moving vehicles, with no holding place at all, sits between Kidnapping and Express Kidnapping
|
||||
- case 7: the file never says how the detention ended
|
||||
- case 7: the loss recorded (nearly 27,000 euros of goods) has nothing to do with the crypto demand (52 BTC, then 300,000 euros), and there is one amount field for both
|
||||
- case 8: a relationship of several prior completed trades, used to set up the robbery, has no label
|
||||
- case 8: the detention rule sits on its edge here: a knife pressed to the chest inside the victim's own car, with no restraint and an immediate flight, reads either as holding to execute the theft or as the snatch in passing the rule excludes
|
||||
- case 9: the victims were the cash side and the sellers had no bitcoin at all, so the loss is fiat and property, which the theft flag cannot distinguish
|
||||
- case 11: there is no way to mark a record whose only source is an untranscribed podcast; only record_only carries it
|
||||
- case 12: no field records a ransom demand the payer could not physically satisfy — the first figure was so large that Lopes assumed a prank and the negotiator had to explain the market's size
|
||||
- case 12: the file says she was handpicked after nine months of planning but never says how the family was found, so the targeting route is unrecorded
|
||||
- case 12: the person held and the person with the keys were different: the target was the holder's wife, and no field records that
|
||||
- case 13: a remote desert spot fits none of the venue values; it is neither premises nor public space in the ordinary sense
|
||||
- case 13: the same article gives two initiation methods — conned into riding in the attackers' car, and pulled out of their own — and the label set records only one
|
||||
- case 14: no label fits a killing with no demand, captivity or negotiation phase; the file describes no extortion of the victim at all
|
||||
- case 14: the file says nothing about what happened between her boarding the vehicle and her death, so the attack pattern itself is unrecorded
|
||||
- case 14: the theft happened online after the victim's death, by impersonation, which no scenario label covers
|
||||
- case 15: the countermeasure that ended the attack — engineering an SOS from his own phone — has no field, although it is the only reason the theft failed
|
||||
- case 16: the money demand was made of the 911 dispatcher as part of the hoax script, not of the victim; there is no field for a demand aimed at no one
|
||||
- case 18: the infant present during some of the robberies, which drew child-abuse counts, has no field
|
||||
- case 19: two hours of mobile detention in a vehicle reads as Express Kidnapping, but the operation was planned around a known holder, which that label excludes
|
||||
- case 20: a forced stop of a moving car sits between the venue categories: the car is the victim's own space but the control was taken on the street
|
||||
- case 20: the report never says how 450 Bitcoins moved once the banking passwords were given up, so the mechanism of the loss has no field
|
||||
- case 21: the loss was hardware whose value keeps generating income for the thieves; the amount fields cannot express that
|
||||
- case 22: the place of captivity is never reported, so venue_of_control cannot be filled
|
||||
- case 22: the ransom was paid in bitcoin by someone the reports cannot identify; there is no field for who paid
|
||||
- case 23: the extortion that followed the robbery, weeks of demands for the device passwords, has no label of its own
|
||||
- case 23: the whole account of the attack is one side's civil pleading, and the schema has no field for the standard of proof behind a case
|
||||
- case 23: three people were attacked in two places minutes apart, one in the lobby and two in the apartment; the schema holds one victim and one venue
|
||||
- case 24: a crypto sale meeting that collapses into gunfire without any theft or theft attempt fits none of the eleven labels; P2P Trade Gone Wrong presumes one party came to steal, and nothing in the file says Royce did
|
||||
- case 24: the man shot at was not the seller but a third party urging the deal on; the schema's single victim field cannot hold that
|
||||
- case 25: the destruction of all the electronic equipment has no place in the six violence categories
|
||||
- case 25: the loss was cash and documents from a safe, with the crypto exposure left unquantified; the labels and the amount fields cannot mark "crypto wealth as the targeting reason, cash as the loss"
|
||||
- case 26: two victims held together, and the schema has one victim field
|
||||
- case 27: a first meeting used to confirm the sum the victim carries, followed by a second meeting set up to rob him, has no field
|
||||
- case 27: the men who lured him and the three who attacked him were different people, which the single label cannot express
|
||||
- case 28: the attack was broken by a hidden fifth employee's phone call, and no field records how it was foiled
|
||||
- case 28: the people held were staff and the intended loss was the company's, which no field distinguishes from an attack on a holder
|
||||
- case 29: a baby kept outside in a pram during the raid, as the Mail on Sunday reported, has no field
|
||||
- case 29: no label records a home invasion carried through to a forced transfer that then failed technically, leaving the raiders with nothing
|
||||
- case 29: the file describes three occupants held, two men and a woman, while the record carries two named victims
|
||||
- case 30: the plot was uncovered by accident, during what officers took for a drug investigation at a hotel, and no field records how an attack came to be foiled
|
||||
- case 30: the restraint kit found on the men — zip ties, duct tape, gloves and bandanas — implies a plan to hold the occupant, which no label can record for an attack that never happened
|
||||
- case 32: a hawala cash ransom running alongside the crypto demand is not recorded anywhere
|
||||
- case 32: the victim's own prosecution for a crypto kidnapping of his own has no field
|
||||
- case 33: forcing liquor on the victim to dress the robbery up as a drunken brawl is a cover-up tactic, which no field records
|
||||
- case 34: forced ingestion of a pill and vodka at the point of release, apparently to delay a police report, has no field
|
||||
- case 34: the detention was mobile and ended in release the same night, which the record's Kidnapping label does not distinguish from a holding at a location
|
||||
- case 35: knife mutilation to force a transfer sits under the Mugging label, which the glossary defines as low-planning opportunistic street crime; the file says nothing about planning either way
|
||||
- case 35: no label records that the loss happened only after the victim first refused
|
||||
- case 39: the broker Mr Pang brought with him was assaulted too, and the schema has one victim field
|
||||
- case 40: the record's victim shot his attacker; no flag records violence by the victim, and a wounded attacker fits nowhere
|
||||
- case 40: whether the unidentified Bitcoin dealer was part of the ambush is left open by the source, so the trade label may be carrying more than the facts support
|
||||
- case 41: the brothers were tied and locked in a room, which neither trade label expresses
|
||||
- case 41: the office was obtained by a second deception, against a shop owner who is a victim with no record of his own
|
||||
- case 42: blocking a victim's exit for a few minutes without tying or locking him in is at the edge of the detention rule
|
||||
- case 43: the six-hour hold was at the victim's own home, so the record's Kidnapping label implies a relocation the source does not report
|
||||
- case 44: the partner and the baby were tied up and threatened as well; the record holds one victim
|
||||
- case 45: a law-enforcement entry that turns out to be lawful has no label; Swatting presumes the emergency report was false
|
||||
- case 45: there is no way to mark a record whose only linked source is about the named person rather than about the incident
|
||||
- case 46: a case the complainant is said to have recanted has nowhere in the record to be marked as disputed
|
||||
- case 48: how long he was held is never stated, which the duration column cannot express
|
||||
- case 49: a ransom note left in the parents' yard for a child victim has no field
|
||||
- case 50: a four-year-old present while a parent is tortured has no field and no flag
|
||||
- case 52: a forced entry that gained no control has no label of its own; Dodged Attack records the outcome but loses the fact that the man was inside the apartment with a shotgun
|
||||
- case 52: no cryptocurrency was demanded in this file, so the case is in the database on the strength of who the victim is
|
||||
- case 52: the victim's own escape by jumping from a second-floor balcony, and the injury risk he took, has no field
|
||||
- case 53: three victims taken on two different days in one operation cannot be expressed
|
||||
- case 53: two different ransom demands in one case, one in bitcoin and one in rupees, have no field
|
||||
- case 55: the venue was the victim's office rather than his home; the glossary's Home Invasion entry covers an office, but the location fields do not record which kind of space it was
|
||||
- case 55: the victim was left bound and had to free himself, which none of the outcome values names precisely
|
||||
- case 56: extortion of an account password, rather than of a holder's funds, has no field
|
||||
- case 59: a killing that happened because the victim recognised the attackers, rather than to coerce him, has no field
|
||||
- case 60: a child victim and child offenders have no field
|
||||
- case 60: the second leg, driving the victim around in a car boot before dumping him, and the simultaneous visit to his family home to extort the money, are one operation that no single label holds
|
||||
- case 61: a partial payment against a much larger demand has nowhere to sit: money_wanted, the demand and the sum paid are three different numbers
|
||||
- case 61: the schema cannot express that the second reported victim turned out, according to police, to be the organiser
|
||||
- case 63: an imitation firearm the victims believed was real has to share the weapons flag with real guns
|
||||
- case 63: forcing victims to open exchange accounts in their own names as a laundering route is not theft of crypto and has no label
|
||||
- case 63: the crime was launched over a road collision, not over the victims' crypto holdings; the schema has no field for motive
|
||||
- case 64: an everyday object improvised as a weapon (a personalised Toblerone bar) can only be expressed through the weapons flag
|
||||
- case 64: the accomplice who never entered the house but received and moved the coins has no place in the schema
|
||||
- case 64: the record has no field for the fact that only the non-participant was convicted while the three raiders are unaccounted for
|
||||
- case 66: there is no way to mark a record that has never been checked against a report; only the record_only field carries it
|
||||
- case 67: a conspiracy broken up by the FBI before any contact is filed as Dodged Attack, but the label reads as if the victim did the dodging
|
||||
- case 67: the schema has no way to mark that the source names the defendants but not the victim, while the record names a victim the source does not
|
||||
- case 68: a single paragraph in a tertiary aggregator is the only source; the schema has no field for source strength
|
||||
- case 68: the file does not say whether the meeting place was public, private or the attacker's own, so the robbery itself cannot be placed
|
||||
- case 69: an investigation dropped for want of evidence has no field of its own
|
||||
- case 70: the label Authority Misuse covers the impersonation of lawful power but not that these were serving officers acting from their real posts
|
||||
- case 70: the schema has no way to record that the detention was papered over afterwards as a lawful arrest for extradition
|
||||
- case 71: a failed ram-raid on unoccupied commercial premises has no label of its own; Dodged Attack is used for the foiled attempt although no victim did any dodging
|
||||
- case 71: the destruction of a neighbouring business that had nothing to do with crypto has nowhere to go in the schema
|
||||
- case 72: planning to kill, prevented before contact, has nowhere to sit in the flags
|
||||
- case 73: an assault that never became a robbery leaves the violence flags carrying the whole incident
|
||||
- case 74: the vehicle theft charged alongside the extortion is a second offence the scenario labels drop
|
||||
- case 74: two victims held in two places by one gang cannot be carried by a single label
|
||||
- case 76: a theft carried out by taking back cash already handed over, inside the buyers' own car, has no label
|
||||
- case 76: the earlier online trade used to build trust is not expressible
|
||||
- case 77: locking the victim in on the way out is detention by the glossary's wording but served the escape, not compliance
|
||||
- case 77: three genuine trades used as grooming before the ambush has no label of its own
|
||||
- case 78: shooting staff without any demand or detention is an armed raid the flags can only record as violence plus weapons
|
||||
- case 78: the label's 'in Public Space' does not fit a private exchange office on the fourth floor of an office tower
|
||||
- case 79: talking a way through the door, which the same article calls both a break-in and a deception, sits between Home Invasion and Malicious Invitation
|
||||
- case 80: sprinkling heroin on the victims and threatening to report them as drug smugglers is a coercion method the violence categories only half-cover
|
||||
- case 80: the FIR's 'along with three others' leaves the victim count unresolved and the labels cannot mark that
|
||||
- case 80: with no holding place and no duration on file, Kidnapping and Express Kidnapping cannot be told apart
|
||||
- case 81: the file never says where he was held, so Kidnapping cannot be separated from detention at his own workplace
|
||||
- case 82: a grab-and-hold lasting seconds sits between the detention rule (anyone held to execute the theft) and its exception for a snatch in passing
|
||||
- case 82: taking the phone that holds the wallet, rather than forcing a transfer, has no label
|
||||
- case 84: armed self-defence by the victim, and the fact that the only firearm was his, has no field
|
||||
- case 85: the theft of cryptocurrency keys rather than a transfer, with no amount ever stated, leaves the loss unquantified
|
||||
- case 86: one man convicted while three others were never identified has no field
|
||||
- case 86: the ransom was demanded from and paid by the victim's mother, which no label or field records
|
||||
- case 88: the post-theft threat to expose the encounter, and the false rape allegation to police, have no field
|
||||
- case 89: police say he was 'targeted after he parked his car' and the gang had a driver and a getaway car, which cuts against Mugging's 'little to no advance planning', but no label covers a planned snatch of a cash bag in a car park
|
||||
- case 90: the on-chain freezing of part of the proceeds has no field
|
||||
- case 91: the release does not say how long the man was in the car or whether it moved, so the difference between Express Kidnapping and a robbery carried out in a parked car cannot be resolved from the file
|
||||
- case 92: the labels cannot express that the physical stage was a bridge into a remote account drain probably carried out by other people
|
||||
- case 93: the whole account is the two victims' as given to one outlet; the labels cannot mark that no police or court record corroborates it
|
||||
- case 96: Costly Fame describes how the victim came to be identified, not what was done to him; there is no label for a street ambush in which nothing was demanded and nothing was taken
|
||||
- case 96: a killing whose motive is inferred from the victim's public profile sits at the edge of the crypto-attack frame
|
||||
- case 99: an inside job by someone with building-site access has no label, and the schema cannot record that the crypto may still be locked inside the stolen safe
|
||||
- case 99: theft of a safe from an empty private house has no label; the eleven scenarios all assume a person is present
|
||||
- case 102: a death caused by a defender's gunfire rather than by the robbers has no label
|
||||
- case 103: the gang got the phone, the tablet and the code but not the coins; the schema has no way to record a wallet that held because a second person was needed
|
||||
- case 103: the maintenance technician — a bystander beaten, bound and held for nearly four hours — is not the record's victim and has no place in the row
|
||||
- case 104: a victim moved through three separate holding places over six days reads as one Kidnapping label
|
||||
- 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 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
|
||||
- case 113: a second victim present only because she happened to be visiting is not expressed by the scenario labels
|
||||
- case 113: the labels have no way to mark an invasion where the crypto objective failed but the violence and the terror did not
|
||||
- case 114: Dodged Attack does not record how the attack was dodged — here the victim physically fought the man off at his home
|
||||
- case 114: the attacker was one of the victim's own subscribers who found his address and followed him for days; stalking by an audience member has no label
|
||||
- case 116: the labels do not mark an extortion that collapsed because the perpetrators feared arrest
|
||||
- case 117: the theft was of cash brought to buy crypto, not of crypto; none of the labels marks which side of the trade the asset was on
|
||||
- case 118: the doorstep package ruse used to get the door open is a deception, but Malicious Invitation / Social Engineering describes luring a victim to the attackers, not tricking them into opening their own door
|
||||
- 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 121: an ambush waiting outside the victim's own front door, on the street rather than inside, sits between Armed Robbery in Public Space and Home Invasion; no label covers the doorstep ambush
|
||||
- case 122: an extortion attempt made through the threat of a criminal case, with no physical element at all, has no violence category to record
|
||||
- case 122: whether the demand succeeded is never stated, so the case cannot be placed as completed or dodged
|
||||
- case 123: a robbery that fails while leaving the victim nearly dead has no label, and no outcome value covers survived-but-severely-wounded
|
||||
- case 123: no cryptocurrency was demanded or taken; the record's own coin_type reads Watch
|
||||
- case 124: an attack allegedly ordered by a rival and carried out by hired men - and, in the November 2021 attempt, by serving sheriff's deputies - has no label; that earlier attempt would be Authority Misuse and sits on no record here
|
||||
- case 124: the victim drove the attackers off with his own firearm, which Dodged Attack does not distinguish from luck or awareness
|
||||
- case 126: both partners were tied and beaten while only the man was forced to transfer - the labels carry one victim role
|
||||
- case 128: a revenge assault by known investors over trading losses has no label; Home Invasion is used because the attack happened at the victim's home
|
||||
- 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 130: how the victim was brought to the guest house is never described, so the initiation method behind the label is unknown
|
||||
- case 134: the article's Rs 1.3 crore is called both a ransom and a transfer obtained under torture, which the labels do not separate
|
||||
- case 136: an attack paid for by a rival in the victim's own online scene - what the article calls violence-as-a-service - has no label
|
||||
- case 136: the target was absent by chance rather than through awareness or defences, which Dodged Attack does not distinguish
|
||||
- case 137: the file gives no duration for the drive, so the brevity that defines Express Kidnapping rests only on the escape when the car stopped
|
||||
- case 138: the record has no field linking the invasions of one crew; the file's second article names Delray Beach and Homestead in September 2022 as two of them (see also 145)
|
||||
- case 138: what the crew was after in Delray Beach is not stated in either excerpt
|
||||
- case 141: how he was lured into the vehicle is not described
|
||||
- case 141: the kidnappers were his own investors trying to recover money they had lost with him; that motive has no label
|
||||
- case 142: grab, extraction of wallet access and release on the same journey also reads as Express Kidnapping, but the source gives no duration
|
||||
- case 143: the address he was sent to was private, so Armed Robbery in Public Space is used for the weapon-and-theft pattern rather than for the venue
|
||||
- case 143: whether the Marktplaats ad was placed by the attackers to select victims is not stated
|
||||
- case 144: that post calls it a kidnapping and abduction, but nothing in the file describes the victims being taken anywhere
|
||||
- case 145: this is one incident in a nine-abduction series by one crew and the record has no field linking it to the others (see also 138)
|
||||
- case 147: Dodged Attack does not express the harm that did occur: the concierge was gagged and tied before the attack was interrupted
|
||||
- case 147: an attack on a company has no label for the building staff member who was the one actually assaulted
|
||||
- case 151: the whole account is a neighbour's Twitter thread, not police or court material
|
||||
- case 151: theft from an unconscious victim, with no confrontation at any point, is only expressible through the Drugs/Alcohol flag
|
||||
- case 152: the earlier attack on the same victim in his driveway on 1 March is a separate incident with no record of its own
|
||||
- case 152: the ransom was demanded from a third party — the crypto trader police believe was the real target — not from the victim or his family
|
||||
- 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: how the two got inside is not reported, so the initiation method has no label
|
||||
- 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
|
||||
- case 164: a raid whose object was the company's servers rather than one holder's wallet has no label
|
||||
- case 166: one victim was airlifted to hospital, which no outcome value among released / escaped / rescued / killed / foiled / unharmed names
|
||||
- case 166: the article is a round-up of at least three Swedish cases; only the Rönninge passage describes this one
|
||||
- case 167: the article never says where the executives were held or how they got free, so the Kidnapping label rests on the single word 'kidnapped'
|
||||
- case 167: the record's victim field holds a company ('Binance Client') while the people attacked were its executives
|
||||
- case 168: part of the group searched the victim's empty apartment while the rest drove him away; the single scenario label cannot carry the second venue
|
||||
- case 168: the victim was abandoned still taped to a post and freed by a passerby, which none of the outcome values names exactly
|
||||
- case 170: the threat to plant drugs on the victim and hand him to police is a coercion method none of the six violence categories covers
|
||||
- case 171: the labels cannot mark an account police have not corroborated; the only facts in the file not coming from the victim are the accident, the severed finger and the alcohol reading
|
||||
- case 171: the source frames the victim's drink-driving against his own story, a stance no scenario or flag can hold
|
||||
- case 172: no holding place other than the van is reported, so the 'unknown or controlled environment' in the Kidnapping definition has nothing behind it
|
||||
- case 172: the detention was mobile and ended with release a kilometre away once the transfer went through, which matches Express Kidnapping more closely than Kidnapping; the source and the charge both call it abduction and illegal detention
|
||||
- case 173: a series of thefts running from March to December against an unstated number of passengers is held in the database as one dated incident
|
||||
- case 173: theft carried out by handling the victim's own unlocked phone, with no violence, no detention and no weapon, has no home among the eleven labels
|
||||
- case 174: a few hours of mobile detention ending in release near the airport also matches Express Kidnapping; the single-category rule forces a choice
|
||||
- case 174: the article never says how the couple got free, so no label or fact field can carry the ending
|
||||
- case 175: a targeted extortion carried out at a cafe table, with no weapon and no detention, fits neither Mugging (which the glossary defines as largely unplanned) nor Armed Robbery (which requires weapons)
|
||||
- case 175: the article reports the victim's allegation and one arrest; the labels cannot mark that the whole account is one complainant's
|
||||
- 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 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
|
||||
- case 180: the four gang members shot and killed on 3 August are outside this incident but sit on the same record
|
||||
- case 180: the report gives no holding place, duration or outcome for the victim, so the label rests on the charge alone
|
||||
- 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 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
|
||||
- case 194: the P2P trading relationship supplied the target intelligence rather than the meeting itself; no label separates target selection from initiation
|
||||
- case 195: online mob retaliation — doxing, tokens made from family photographs, and an alleged pet theft — has no label; none of the eleven scenarios covers a case in which no person was physically approached
|
||||
- case 195: the record treats the dog as the detained party; the detention flag has no way to express that
|
||||
- case 196: the crypto and card losses were discovered after the event, drained with the stolen phone and wallet rather than taken at the scene; no label covers the follow-on account theft
|
||||
- case 197: an ambush sprung at the lure's own meeting place, with the transfer forced on the spot, is not expressed by the Malicious Invitation label alone
|
||||
- case 199: a case in which police end up doubting the complainant has no way to be marked
|
||||
- case 199: a fake police roadblock used to stop a moving car has no label of its own; Authority Misuse covers the impersonation but not the vehicle interception
|
||||
- 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 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 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 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
|
||||
- case 259: the meeting with "unidentified investors" is the only account of the lure, and the report attributes it to nobody
|
||||
- case 259: the report says the couple were kidnapped and killed but locates neither the detention nor the killing, so venue and duration cannot be filled
|
||||
- case 260: the doubts raised publicly about the account have nowhere to sit in the schema
|
||||
- case 260: the whole account is the victim's own inference — "must have gotten jumped" — with no police statement on file, and no field records that uncertainty
|
||||
- case 318: no field records that the targeting rested on a misreading of his forum moderation, or that his actual holdings were about $10,000
|
||||
- case 318: the consequences the file dwells on — a family in hiding, youth protection involvement, savings spent — have no place in the schema
|
||||
- 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 357: the £450,000 watch was the larger single loss and no field separates it from the crypto
|
||||
- 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
|
||||
- case 360: neither report says how long the victim was tied up or how he got free
|
||||
- case 361: no field records that the attempt was broken by police already at the scene rather than by anything the victims did
|
||||
- case 361: the weapons flag cannot distinguish replica devices from real ones — the grenades were airsoft and the bomb technicians said they could not cause serious damage
|
||||
- case 363: the crew's size differs by source — two men entering per the district attorney, four per the LA Times, six per the Independent, with a sixth never identified — and no field records it
|
||||
- case 363: the fake-police entry and the holding of two people in the apartment are one event, and only one scenario label rides on the record
|
||||
- case 363: the victim was 17 and nothing in the record marks that he was a minor
|
||||
- case 366: the case was transferred to another country's jurisdiction because extradition was impossible, which the record has no field for
|
||||
- case 366: the victim was killed after the wallets were emptied, which the initiation-based labels do not express
|
||||
- case 373: filmed captivity used as leverage on a third party is not expressible in the labels
|
||||
- case 374: two of the six suspects are minors, which the record cannot express
|
||||
- case 375: nothing crypto was taken: the loss is the cash staked for a purchase, which the database's crypto fields cannot hold cleanly
|
||||
- case 375: the ambush landed during an in-person cash-for-crypto trade, but the file does not say whether the counterparty took part, so P2P Trade Gone Wrong cannot be assigned
|
||||
- case 376: the victim is a child and not a crypto holder: cryptocurrency is the rail the ransom was paid on, not the asset targeted, which none of the scenario labels expresses
|
||||
- case 377: one hostage released and the other killed in the same operation has no label
|
||||
- case 377: the file does not settle whether the couple were seized at their own home or ambushed elsewhere, so the boundary with Home Invasion stays open
|
||||
- case 379: the victim was killed in captivity without any payment being reported, which the initiation-based labels do not express
|
||||
- case 379: three people abducted alongside the target and held as a by-product of the operation have no label of their own
|
||||
- case 380: Livecoins calls the scene both the victim's office and a residence, so the venue under Home Invasion is unsettled
|
||||
- case 380: the lead came from tradesmen who heard the victim mention Bitcoin at her own premises months earlier; no label covers a contractor's tip-off
|
||||
- case 381: the article does not say how long the couple were held or how the captivity ended, so the pattern under Home Invasion is only partly described
|
||||
- case 382: Dodged Attack records that the raid failed but not that knives were drawn and the owner was injured repelling it
|
||||
- case 383: a break-in to lift a hardware wallet, with no person in the account at all, fits none of the eleven labels, which all describe attacks on people (compare 3, 6, 21, 99)
|
||||
- case 383: the record is one incident carved out of a racketeering indictment, and there is no way to mark that the amount, the arrests and the outcome belong to the enterprise rather than to this break-in
|
||||
- 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 386: the victim's death fifteen months later is a separate event that this record can neither connect nor disconnect, although the family raised it in the same breath
|
||||
- case 387: the cryptocurrencies were her partner's and she was the one tied up and held; the single victim field cannot show that split
|
||||
- case 387: what was on the USB key, and whether any cryptocurrency was ever moved with it, is never reported
|
||||
- case 388: two children were tied alongside their parents and have no field of their own; the victim field carries all four
|
||||
- case 388: whether anything was actually taken is never reported, so the theft flag cannot separate a completed robbery from an aborted one
|
||||
- case 389: control was seized inside his own home and he was moved away at once, so the home phase of the attack carries no separate label
|
||||
- case 389: whether the attackers got anything is never reported, which the theft flag cannot express
|
||||
- case 390: the crypto nexus of this case is carried only by the headline of a source whose text could not be retrieved, and nothing in the schema can mark a record whose crypto link is unverified
|
||||
- case 390: the prosecutors' own qualification is attempted extortion plus theft with violence — an extortion that failed while the theft succeeded — which no single label expresses
|
||||
- case 391: the threat to take him out of the country and sell his organs is coercion with no category of its own between Violence/Torture and Weapons
|
||||
- case 392: the intended target was the son, who was never touched; neither the victim field nor the labels can record an attack aimed at a holder through his parents
|
||||
- case 393: a family with three children held together to extract one access code has no label distinguishing it from a single-victim invasion
|
||||
- case 393: neither article says how the 40 minutes ended, whether the code was handed over, or whether anyone was hurt - three of the record's six flags have nothing to rest on because the report is two paragraphs long
|
||||
- case 394: nothing in the schema marks a case in which the database's victim is himself the alleged offender
|
||||
- case 395: he was moved about ten floors up inside his own building and never taken out of it, so neither Kidnapping (taken away to another place) nor Home Invasion (held in his own space) fits cleanly
|
||||
- case 397: the impersonation of Income Tax officers that the record's Authority Misuse label rests on appears nowhere in this case's file
|
||||
- case 397: the only narrative of the kidnapping on file is a party spokesperson's press conference; there is no field to mark a case whose account is political rather than police or judicial
|
||||
- case 398: neither article says where Mavani was held or for how long, so nothing in this file carries the record's farmhouse and multi-day captivity
|
||||
- case 399: there is no field for a case whose only source is the victim's own report to Gart Research; record_only carries it but does not distinguish a missing source from a first-hand one
|
||||
- case 400: the crypto element is an unauthenticated ransom note sent to a newsroom; nothing in the schema marks a case whose crypto connection is itself unverified
|
||||
- case 401: the initiation (a forced entry at 3 a.m.) and the captivity (a lock-up 90 kilometres away in another department) belong to two different labels, and the record's single scenario field has to pick one
|
||||
- case 401: the women held are not the crypto holder - the target was the partner's business - and the labels describe the holder, not the household used as leverage
|
||||
- case 402: the two who entered say they were themselves coerced over Signal by handlers who never appear at the scene; there is no label or field for a directed or outsourced attacker
|
||||
- case 403: full recovery of the stolen crypto within 72 hours and its return to the victim has no field
|
||||
- case 403: the theft of a car alongside the crypto, and the car being what caught them, has nowhere to sit
|
||||
- case 404: an invasion that takes devices but fails to get the transfer sits between Home Invasion and Dodged Attack, and the schema has no half-measure
|
||||
- case 404: the daughter separated into another room as leverage against her father has no label and no field
|
||||
- case 404: three victims in one household are held in one victim field
|
||||
- case 405: an invasion that succeeds against the premises and fails against the person has no single label; it is both a home invasion and a dodged attack
|
||||
- case 405: one commando and two addresses on the same morning are held as two records with no link field between them
|
||||
- case 405: the neighbour whose door was forced and who was made to give up the apartment number is the only person the attackers reached, and the schema's victim field holds the absent executive instead
|
||||
- case 406: an assault to extract an address, with nothing demanded of the victim herself, sits oddly under Home Invasion, and RTL does not say the men entered her home
|
||||
- case 406: an attack on the wrong address, against someone with no connection to crypto, has no label
|
||||
- case 406: one commando and two victims on the same morning are held as two records with no link field between them
|
||||
- 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 407: the corrupt traffic stop and the abduction are one operation run by one gang, and the schema takes a single primary scenario
|
||||
- case 408: a killing that ends a robbery, rather than a ransom negotiation, has no label of its own
|
||||
- case 408: a woman who passed on the victim's whereabouts without being described as part of the attack has no place in the schema, and no label covers an informant
|
||||
- case 408: the abduction itself is nowhere in this file, so the label rests on the gap between where he vanished and where he was buried
|
||||
- case 409: a case whose only account of the physical attack is the victim's own X posts, with two outlets attributing the loss to address poisoning instead, has no way to be marked as uncorroborated
|
||||
- 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 409: the one word that might carry a label is the victim's own 'kidnapping' inside a list of elements, which a second outlet renders as a threat rather than an event
|
||||
- case 410: a payment extracted under threat of arrest and deportation, with no weapon and no violence, has no category between extortion and robbery — the same argument the victims' lawyer is making about the charge
|
||||
- case 410: eight victims held together in one incident cannot be expressed; the record's victim field holds them as a group
|
||||
- case 410: the raid was an on-site detention inside the victims' rented home, which Home Invasion would describe, but the entry was made under colour of law and Authority Misuse carries the case
|
||||
- case 411: a case where the central facts rest on a ransom video and unnamed sources, with no official confirmation and a live suggestion of staging, has no way to be marked as such
|
||||
- case 411: a location exposed by a companion's geotagged post is not Costly Fame, which turns on the victim's own public profile
|
||||
- case 411: an abduction over an alleged criminal debt, where the ransom is framed as repayment rather than a price, has no label
|
||||
- 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 412: an attack that begins in a hotel room of unstated ownership and then moves the victim to a second address fits Home Invasion and Kidnapping in halves, and the schema takes one
|
||||
- case 413: an attack that completed the forced entry and the assault but never reached the payment sits between Home Invasion and Dodged Attack; the labels force a choice
|
||||
- case 414: the fourth man directing the operation by phone from elsewhere has no place in the labels
|
||||
- case 415: nothing in the labels records that the address was wrong — the household had no connection to cryptocurrency at all
|
||||
- case 415: the remote instigator directing the two men by phone has no place in the labels
|
||||
- case 416: small explosives used as a door-opening tool fit awkwardly under the weapons category and have no scenario label
|
||||
- case 416: two attacks by the same crew within half an hour are held as separate cases; nothing in the labels links them
|
||||
- case 417: forced entry into the home and a blow to the head are more than Dodged Attack conveys, but the intruders never took control, so Home Invasion does not fit either
|
||||
- case 418: Spanish sources call it a "secuestro exprés" while the plan was a transfer to Alicante for torture — the two glossary labels Kidnapping and Express Kidnapping pull in different directions
|
||||
- case 418: the abduction was completed but the extortion never happened; the labels record one scenario and cannot show that the operation was broken minutes in
|
||||
- case 419: "fleeing under pressure from their victims" implies a confrontation the labels cannot describe
|
||||
- case 421: the file disagrees with itself on whether the men got as far as forcing the building door, which is what separates an attempt at the threshold from a break-in
|
||||
- case 421: the plot was broken by a concierge, not by the victims, and Dodged Attack carries a suggestion of victim awareness this case does not support
|
||||
- case 422: Dodged Attack does not express that the attacker had already drawn a gun and landed a blow before the interruption
|
||||
- case 424: a remote third party directing the violence by phone is not expressible
|
||||
- case 424: an extortion broken off by chance (a passing helicopter) rather than by the victim has no label
|
||||
- case 425: a kidnapping used to recover money the gang could not launder, rather than to rob the victim, has no label
|
||||
- case 425: a victim who is himself under investigation has no place in the schema
|
||||
- case 426: the man who was approached had no reported connection to cryptocurrency
|
||||
- case 426: the real target was never approached, and the label set has no way to mark a victim who was targeted but never met
|
||||
- case 427: an attack on the wrong or absent holder has no label
|
||||
- case 427: the target was absent and the household was held in his place; the labels do not mark proxy victims
|
||||
- case 428: a child as a co-hostage is not expressible
|
||||
- case 428: the transfer delay that made the gang switch from on-site extortion to hostage-taking has no label
|
||||
- case 429: an attack that gains control inside the home and is then broken by the victim fits neither Home Invasion nor Dodged Attack cleanly
|
||||
- case 430: one incident inside a 14-defendant, multi-state prosecution has no label for its place in the series
|
||||
- case 430: the record's claim that the gang failed to find the bitcoin has no counterpart in the labels
|
||||
- case 431: children among the detained victims is not expressible
|
||||
- case 431: the holder was absent and his family was held in his place; the labels do not mark proxy victims
|
||||
- case 432: a rescued victim who turns out to be wanted himself has no place in the schema
|
||||
- case 432: the roadside interception that starts the abduction has no label of its own
|
||||
- case 433: a first approach at his door four days earlier, which he repelled by shutting it, is folded into the same record as the car incident
|
||||
- case 433: the aftermath has nowhere to go: a family in hiding between short-term rentals, the accused on house arrest, a youth-protection referral
|
||||
- case 433: the defensive measures decided the outcome — the bear spray bought after the first approach, the call to police kept open — and nothing records that
|
||||
- case 434: a whole case told only through the victim's father has no way to be marked as second-hand
|
||||
- case 434: the ride-hailing trip as the point of interception has no label; the driver's petrol-pump stop is the hinge of the whole attack and nothing records whether the driver was involved
|
||||
- case 435: a case known only through a prosecutor's aggregate statement has no way to record that the facts themselves are unreported
|
||||
- case 435: the file has a charge sheet and no incident: no victim, no venue, no duration, no amount, no account of how it happened
|
||||
- case 435: two of the three accused are charged over a second kidnapping a month later at the other end of the country; the serial offender has no label
|
||||
- case 436: recruitment of young men by a named criminal organisation has no label
|
||||
- case 436: the sources give a violent sequestration at the victim's home with no entry method at all, so the initiation of the attack is unlabelled
|
||||
- case 437: a haul abandoned during the escape leaves the theft flag ambiguous
|
||||
- case 437: a household with no link at all to cryptocurrency, attacked on bad intelligence, has no label
|
||||
- case 438: a contract accepted over social media by men who did not all know each other has no label
|
||||
- case 438: four children and a music teacher were in the house; the record holds one victim
|
||||
- case 438: the attack broke off when a suspect shot his own accomplice, and no label carries an invasion that collapsed on itself
|
||||
- case 442: a second team that waited outside and afterwards searched the first team to collect the proceeds has no label
|
||||
- case 442: the record holds one victim; the source says someone inside opened the door and does not say whether that was the same person who was held
|
||||
- case 443: a case where the crypto connection is the son's wealth rather than the victim's own holdings is not expressible
|
||||
- case 443: impersonation of the victim by text for more than a month, and the stripping and attempted letting of his house, have no label
|
||||
- case 444: a victim held in a stationary van in woodland is neither a premises nor a vehicle in motion
|
||||
- case 445: the first of two attempts on the same victim cannot be told apart from the second in any source on file
|
||||
- case 447: an attempt broken off by third parties (neighbours) rather than by the victim sits awkwardly inside Dodged Attack
|
||||
- case 449: a theft carried out as the physical arm of an online social-engineering enterprise has no label of its own
|
||||
- case 450: remote iCloud tracking of the victim as the trigger for a physical break-in has no label
|
||||
- case 450: the file does not say whether the wallet was found, so neither a completed theft nor a dodged attempt can be asserted
|
||||
- case 453: a robbery the attackers said they had been hired to carry out, to recover money the victim was accused of stealing, has no field
|
||||
- case 453: a sixth man coaching the raid by telephone, because the five inside could not operate the wallets, has no field
|
||||
- case 453: the same cell's two other robberies sit in the same police release with no case-link field
|
||||
- case 454: five men were in the room and four have been charged; the file does not account for the rest
|
||||
- case 454: the record's "garage" is not in the file, which says only a room
|
||||
- case 455: an extortion that failed on where the password was stored, while other property was taken, has no label
|
||||
- case 455: threats made after the release to force him to drop his complaint have no field
|
||||
- case 456: an escape into woodland mid-operation, and the pressure applied through a third person advising by phone, have no field
|
||||
- case 456: how the attackers identified him is not established; the targeting rests on the victim's belief and on the demand coming within seconds of the abduction
|
||||
- case 456: the three sources give three different elapsed times before he was found, so no single duration fits
|
||||
- case 457: one night's series of three addresses is split across separate records with no link field
|
||||
- case 458: a transfer interrupted mid-execution is neither completed theft nor an attempt in the flag set
|
||||
- case 458: the file gives no duration for the detention
|
||||
- case 459: a ransom demanded to recover a claimed debt, rather than to enrich the attackers, has no field
|
||||
- case 459: sexual violence, which every article puts at the centre of the case, has no violence category
|
||||
- case 459: the record's single date cannot hold the gap the police account opens between the 29 June arrival and an abduction after days of travelling together
|
||||
- case 459: the victims were held at a house the attackers rented for the purpose, which the Kidnapping label covers only by convention
|
||||
- case 460: a second device fetched from the victim's villa while he was held elsewhere spans two venues that one venue field cannot hold
|
||||
- case 460: about 30 hours of captivity falls between the hours and days buckets
|
||||
- case 461: a demand for one named hardware-wallet device, rather than for an amount, has no field
|
||||
- case 462: an impersonation staged for a camera, with hotel staff filming it as a legitimacy prop, has no field
|
||||
- case 462: the file never says how long he was held, so the brevity that separates Express Kidnapping from Kidnapping rests on the same-day release alone
|
||||
- case 463: one victim was released and the other allegedly passed to a second group for further extortion; the schema has one outcome per record
|
||||
- case 463: the cannabis purchase that brought the pair to the ambush point is not covered by any label, and no source says who set the meeting up
|
||||
- case 464: he was lured to and held at an attacker's own room, which the batch convention files as Kidnapping although nobody was taken anywhere — he came on the invitation and was held where he arrived
|
||||
- case 464: the record's single scenario field cannot carry both the lure and the confinement
|
||||
- case 465: the only source is two sentences inside a round-up about a different case (464), so most of the record's detail has nothing behind it
|
||||
- case 465: the £250,000 covers a watch and bitcoin together; the amount fields cannot express a combined loss
|
||||
- case 466: the place of detention is never stated in any source, so venue_of_control cannot be filled
|
||||
- case 466: the record's date is the arrival and abduction, while the deaths were discovered four days later
|
||||
- case 467: the only article on file uses pseudonyms, so the victim field carries no real identity
|
||||
- case 469: the file never says whether the occupant was present, so the record cannot state what she experienced
|
||||
- case 470: the sources do not agree whether the first team actually got inside, and the labels have no in-between state
|
||||
- case 471: the record's 'remote mastermind' watching the Snapchat stream appears in no article on file
|
||||
- case 473: both sources are single-sentence round-up entries, so the whole case rests on two lines and nothing can be said about how the attempt ended
|
||||
- case 474: five people were in the house and three adults were bound; the record holds one victim entry
|
||||
- case 474: the father freeing himself and ending the attack before any transfer is the turn of the case and no label carries it
|
||||
- case 474: the ringleader directing from a distance and recruiting through encrypted messaging has no field
|
||||
- case 475: the exchange's duress detection ending the theft mid-crime has no field
|
||||
- case 475: the victim's amnesia means the file cannot say how long he was held or exactly what was done
|
||||
- case 476: the decoy role - a man who makes the call and is deliberately absent from the ambush - has no field
|
||||
- case 476: the victim was lured to and held at premises the attackers controlled rather than taken there by force, so Kidnapping is applied by the file's convention for that pattern and the gap is noted here
|
||||
- case 477: how long either victim was held is not reported, so the difference between an express pattern and a longer detention cannot be recorded
|
||||
- case 477: no label distinguishes a case where the detention began at home and ended with the victims abandoned kilometres apart
|
||||
- case 477: the two victims were separated and left in different places, which neither label expresses
|
||||
- case 478: a young child present through the whole detention has no field of its own
|
||||
- case 478: the attack ending because neighbours heard cries and police arrived, with nothing taken, is not expressible in the labels
|
||||
- case 478: the case may rest on a wrong belief that the couple held crypto at all - no label covers targeting on bad data
|
||||
- case 479: a robbery broken off by a 911 call and arriving sirens, with the attackers caught minutes later, has no label of its own
|
||||
- case 480: the intended target was absent throughout, so the record's victim field and the label both describe people the attack was not aimed at
|
||||
- case 480: the wrong-address case - people with no link to cryptocurrency held in place of the holder whose address the attackers had - has no label
|
||||
- case 481: a child survivor left unharmed in the flat has no field
|
||||
- case 481: entry was gained through a trusted business relationship with no forced entry, which the Home Invasion definition's 'forcibly enter' does not cover and no other label carries
|
||||
- case 481: the killing of the family dog is charged separately as animal cruelty and no field records it
|
||||
- case 481: the unborn child counted in the prosecutors' charge of interrupting the pregnancy has no place in the six violence categories
|
||||
- case 482: the mismatch between the 6 million euros the attackers expected and the roughly 3,000 euros in reach - targeting on bad data - has no label
|
||||
- case 482: the victim freeing himself and ending the attack is the turn of the case and no label carries it
|
||||
- case 483: detention that was lawful in itself, and then became the instrument of the theft, cannot be distinguished from detention by criminals
|
||||
- case 483: the record cannot say how many victims there were, and the victim field carries only "Multiple detainees"
|
||||
- case 484: a crime that reaches the record months later through the victim's own stream, with no official confirmation of anything, has no evidence-quality field
|
||||
- case 484: the sequence cannot show that the violence and the gasoline continued after it was clear there was no crypto to take
|
||||
- case 484: the target was chosen for holdings he did not have, and no field records an attack built on a wrong guess
|
||||
- case 485: the case is entangled with an exchange collapse, a second missing executive and 4,500 BTC of disputed reserves, none of which an attack label expresses
|
||||
- case 485: the file cannot say whether the business meeting at the fuel depot was the lure
|
||||
- case 485: there is no outcome value for a victim who was never found and has not been declared dead
|
||||
- case 486: a victim who escaped from a robbery that had already succeeded has no outcome that fits cleanly
|
||||
- case 486: the record cannot hold the split between the crypto ($562,155) and the jewellery (about $413,500)
|
||||
- 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
|
||||
|
||||
## Cases to decide on scope, merge or split
|
||||
|
||||
No scenario label fits (mostly empty premises, unattended machines and burglaries with nobody present) — decide whether a physical-attack database keeps them: [3, 6, 10, 21, 24, 57, 62, 99, 101, 105, 112, 195, 198, 349, 383, 409, 449, 450, 468]
|
||||
|
||||
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]
|
||||
|
||||
Record-only (restructured from the DB record; nothing to verify against): [11, 45, 66, 399]
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,148 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Consolidate the verification batches into batches/VERIFICATION-REPORT.md and
|
||||
batches/contradictions-ALL.md. Re-run after every apply_batch.py."""
|
||||
import json, glob, re, collections, datetime
|
||||
BASE='batches/'
|
||||
cases=[]
|
||||
for f in sorted(glob.glob(BASE+'batch-[0-9]*.json')):
|
||||
n=int(re.search(r'batch-(\d+)',f).group(1))
|
||||
for c in json.load(open(f,encoding='utf-8')):
|
||||
c['_batch']=n; cases.append(c)
|
||||
byid={c['id']:c for c in cases}
|
||||
seqs=json.load(open('scenario-sequences.json',encoding='utf-8'))
|
||||
db=json.load(open('../attacks-export-Gart-website.json',encoding='utf-8'))
|
||||
recs=db if isinstance(db,list) else db.get('data',db)
|
||||
dbids={int(r['id']) for r in recs}
|
||||
name={int(r['id']):(r.get('victim') or r.get('name') or '') for r in recs}
|
||||
ov=json.load(open('summary-overrides.json',encoding='utf-8'))
|
||||
fp=json.load(open(BASE+'flag-proposals.json',encoding='utf-8'))
|
||||
today=datetime.date.today().isoformat()
|
||||
|
||||
THEMES=[
|
||||
('Repeat victimisation / several incidents on one record', r'repeat|same household|consecutive days|second event|previous occasions|campaign|similar incident|one record|single record|carried on the same'),
|
||||
('Insider, intimate or acquaintance perpetrator', r'insider|intimate|family member|own driver|own bodyguard|acquaintance|friend|relative'),
|
||||
('Empty premises, unattended machines, infrastructure', r'empty premises|unattended|burglar|ATM|machine|infrastructure|mining|premises were empty|nobody home|no one home'),
|
||||
('Extortion at a distance or threat at the door without entry', r'at a distance|without entry|at the door|no physical contact|Telegram|blackmail|threat only|extortion by'),
|
||||
('Lured to and held at the attackers\' venue (captivity without transport)', r"attackers' (venue|premises|apartment|rented)|captivity without transport|held at the attackers|attackers' own"),
|
||||
('Delivery, disguise or uniform ruse (mislabelled as Authority Misuse or Malicious Invitation)', r'delivery|disguise|uniform|DoorDash|courier|parcel|pretext'),
|
||||
('Preparation: leaks, surveillance, trackers, data breaches', r'leak|surveillance|tracker|reconnaissance|preparation|data breach|breach|OSINT|knew about'),
|
||||
('Drugging as the approach', r'drugg|drug as|sedat|spiked'),
|
||||
('Unexplained death or undetermined circumstances', r'undetermined|unexplained|death with|cause of death|disappear'),
|
||||
('Security measures deciding the outcome', r'security measures|guard|alarm|safe room|CCTV|panic'),
|
||||
('Scope: fraud, non-violent, or not crypto-linked', r'fraud|non-violent|borderline|out of scope|scope|not crypto'),
|
||||
('Multiple victims on one record', r'eleven victims|several victims|victims robbed in one|two intended victims|group of'),
|
||||
]
|
||||
def theme(g):
|
||||
for t,rx in THEMES:
|
||||
if re.search(rx,g,re.I): return t
|
||||
return 'Other'
|
||||
gaps=collections.defaultdict(list)
|
||||
for c in cases:
|
||||
for g in c.get('gaps') or []:
|
||||
gaps[theme(g)].append((c['id'],g))
|
||||
|
||||
# contradictions
|
||||
FIELDMAP={'detention flag':'detention','kidnappings':'detention','held_duration':'detention','detention duration':'detention','held duration':'detention','duration':'detention','deaths':'life_taken','theft flag':'theft','crypto stolen':'theft','property taken':'theft','arrest':'arrests','charges':'arrests','sentence total':'arrests','attacker name':'attackers','attribution':'attackers','victim age':'victim','victim role':'victim','victim employer':'victim','age':'victim','role':'victim','children':'victim','time':'date','coin':'coin_type','violence_torture':'violence','injuries':'violence','drugs':'drugs_alcohol','summary (site)':'site summary','venue':'location','status':'status','certainty':'status','sequence of events':'description','attack method':'description','circumstances':'description','who raised the alarm':'description','reports':'description','source url':'notes','flags':'flags'}
|
||||
def norm(f):
|
||||
f=f.strip().lower()
|
||||
base=re.split(r'\s*[/(]\s*',f)[0].strip()
|
||||
return FIELDMAP.get(f,FIELDMAP.get(base,base))
|
||||
ctr_field=collections.Counter(); ctr_case=collections.Counter(); ctr_total=0
|
||||
for c in cases:
|
||||
for ct in c.get('contradictions') or []:
|
||||
ctr_total+=1; ctr_field[norm(ct.get('field','?'))]+=1; ctr_case[c['id']]+=1
|
||||
|
||||
# flags
|
||||
fl=collections.Counter((p['flag'],str(p['record']),str(p['proposed'])) for p in fp)
|
||||
det_up=sorted(p['id'] for p in fp if p['flag']=='kidnappings' and str(p['proposed'])=='1')
|
||||
det_down=sorted(p['id'] for p in fp if p['flag']=='kidnappings' and str(p['proposed'])=='0' and str(p['record'])=='1')
|
||||
life=[p for p in fp if p['flag']=='life_taken']
|
||||
|
||||
# sequences
|
||||
lab=collections.Counter(); multi=[]; empty=[]; unsup=[]; dodged=[]
|
||||
for k,v in seqs.items():
|
||||
sq=v.get('sequence') or []
|
||||
for l in sq: lab[l]+=1
|
||||
if len(sq)>1: multi.append(int(k))
|
||||
if not sq: empty.append(int(k))
|
||||
if v.get('v1_label_supported') is False: unsup.append(int(k))
|
||||
if 'Dodged Attack' in sq: dodged.append(int(k))
|
||||
|
||||
record_only=sorted(c['id'] for c in cases if c.get('record_only'))
|
||||
SCOPE_RX=r'belongs in this database|place in a crypto database|belongs in a K&R database|belongs in a physical-attack database|borderline for a physical|not crypto-related|candidate for removal|no person was held or attacked|nothing was stolen or demanded|lawful|doxing'
|
||||
scope=sorted({c['id'] for c in cases if re.search(SCOPE_RX,(c.get('notes_for_sofia') or '')+' '+(c.get('rationale') or '')+' '.join(c.get('gaps') or []),re.I)})
|
||||
nobody=sorted(i for i in empty if i not in record_only)
|
||||
MERGE_RX=r'same incident|duplicate of|split across|split by hand|splitting this record|is a merge of|same operation is split|may be separate records|rest on the same paragraph|separate records with no link'
|
||||
merge=sorted({c['id'] for c in cases if re.search(MERGE_RX,(c.get('notes_for_sofia') or '')+' '.join(c.get('gaps') or []),re.I)})
|
||||
|
||||
out=[]
|
||||
w=out.append
|
||||
w(f"# Verification report — all batches ({today})\n")
|
||||
w("Every summary, scenario sequence, flag proposal and contradiction below was written from the case's own dossier (sources/<id>_*.txt) by a writer agent and checked line by line by a read-only checker. The DB export is untouched: everything here is a proposal for Sofia. Per-batch detail sits in contradictions-NN.md; the merged list is contradictions-ALL.md.\n")
|
||||
w("## Coverage\n")
|
||||
w(f"| Item | Count |\n|---|---|")
|
||||
w(f"| Cases in the DB export | {len(dbids)} |")
|
||||
w(f"| Cases with a verified summary (summary-overrides.json) | {len(ov)} |")
|
||||
w(f"| Cases with a scenario sequence (scenario-sequences.json) | {len(seqs)} |")
|
||||
w(f"| Cases verified in batches 01–{max(c['_batch'] for c in cases):02d} | {len(cases)} |")
|
||||
w(f"| Cases still without a verified summary | {len(dbids-{int(k) for k in ov})} {sorted(dbids-{int(k) for k in ov}) or ''} |")
|
||||
w(f"| Record-only cases (no usable article on file) | {len(record_only)} {record_only} |")
|
||||
w("")
|
||||
w("## Contradictions between record and articles\n")
|
||||
w(f"{ctr_total} contradictions across {len(ctr_case)} cases. None was resolved; each is quoted with the article line in contradictions-ALL.md.\n")
|
||||
w("| Field | Contradictions |\n|---|---|")
|
||||
for k,n in ctr_field.most_common(): w(f"| {k} | {n} |")
|
||||
w("")
|
||||
w("Cases with the most contradictions (each needs a full re-entry):\n")
|
||||
for i,n in ctr_case.most_common(20): w(f"- case {i} ({name.get(i,'')}): {n}")
|
||||
w("")
|
||||
w("## Flag proposals\n")
|
||||
w(f"{len(fp)} proposals on {len({p['id'] for p in fp})} 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.\n")
|
||||
w("| Flag | Record | Proposed | Count |\n|---|---|---|---|")
|
||||
for (f_,r,p),n in sorted(fl.items(),key=lambda x:(x[0][0],-x[1])): w(f"| {f_} | {r} | {p} | {n} |")
|
||||
w("")
|
||||
w(f"Detention (DB field kidnappings) 0/null → 1 under the owner's rule ({len(det_up)}): {det_up}\n")
|
||||
w(f"Detention 1 → 0 ({len(det_down)}): {det_down}\n")
|
||||
w("Fatality flag (life_taken) proposals:\n")
|
||||
for p in life: w(f"- case {p['id']}: {p['record']} → {p['proposed']} — {p['evidence']}")
|
||||
w("")
|
||||
w("## Scenario sequences\n")
|
||||
w(f"| Item | Count |\n|---|---|\n| Cases with more than one label in sequence | {len(multi)} |\n| Cases where the v1 label is not supported by the file | {len(unsup)} |\n| Foiled attacks (Dodged Attack) | {len(dodged)} |\n| Cases no label fits (empty sequence) | {len(empty)} |\n")
|
||||
w("Label frequency across all sequences:\n")
|
||||
w("| Label | Uses |\n|---|---|")
|
||||
for l,n in lab.most_common(): w(f"| {l} | {n} |")
|
||||
w("")
|
||||
w("Cases no label fits, with the writer's reason:\n")
|
||||
for i in sorted(empty):
|
||||
r=(seqs[str(i)].get('rationale') or '').strip().replace('\n',' ')
|
||||
w(f"- case {i} ({name.get(i,'')}): {r[:260]}")
|
||||
w("")
|
||||
w("## Label gaps (what the eleven scenarios cannot express)\n")
|
||||
w("Gap notes grouped by theme. Counts are notes, not cases; a case can raise several.\n")
|
||||
w("| Theme | Notes | Cases |\n|---|---|---|")
|
||||
for t,_ in THEMES+[('Other','')]:
|
||||
items=gaps.get(t,[])
|
||||
if not items: continue
|
||||
ids=sorted({i for i,_ in items})
|
||||
w(f"| {t} | {len(items)} | {', '.join(map(str,ids))} |")
|
||||
w("")
|
||||
w("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).\n")
|
||||
for t,_ in THEMES+[('Other','')]:
|
||||
items=gaps.get(t,[])
|
||||
if not items: continue
|
||||
w(f"### {t}\n")
|
||||
for i,g in sorted(items): w(f"- case {i}: {g}")
|
||||
w("")
|
||||
w("## Cases to decide on scope, merge or split\n")
|
||||
w(f"No scenario label fits (mostly empty premises, unattended machines and burglaries with nobody present) — decide whether a physical-attack database keeps them: {nobody}\n")
|
||||
w(f"Writer questioned scope for another reason (not crypto-related, lawful entry, doxing only, argument during a sale, non-violent device theft): {scope}\n")
|
||||
w(f"Possible merges or splits (same incident across records, or several incidents on one record): {merge}\n")
|
||||
w(f"Record-only (restructured from the DB record; nothing to verify against): {record_only}\n")
|
||||
open(BASE+'VERIFICATION-REPORT.md','w',encoding='utf-8').write('\n'.join(out))
|
||||
|
||||
# merged contradictions
|
||||
parts=[]
|
||||
for f in sorted(glob.glob(BASE+'contradictions-[0-9]*.md')):
|
||||
parts.append(open(f,encoding='utf-8').read())
|
||||
open(BASE+'contradictions-ALL.md','w',encoding='utf-8').write(f"# All contradictions, flag proposals and notes for Sofia — merged from every batch ({today})\n\n"+'\n\n'.join(parts))
|
||||
print('report:',len(out),'lines; cases',len(cases),'contradictions',ctr_total,'flag proposals',len(fp),'gap notes',sum(len(v) for v in gaps.values()))
|
||||
Reference in New Issue
Block a user