docs(verify): finer gap themes in the verification report

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZZENdTLzNGsbNy4DyF1yt
This commit is contained in:
StellarCrow
2026-09-30 12:37:32 +02:00
co-authored by Claude Fable 5.1
parent 6cfa0b19c9
commit d870f17015
2 changed files with 98 additions and 64 deletions
+91 -63
View File
@@ -209,7 +209,14 @@ Gap notes grouped by theme. Counts are notes, not cases; a case can raise severa
| Unexplained death or undetermined circumstances | 12 | 26, 58, 207, 295, 392, 400, 443, 467, 468, 485 |
| Security measures deciding the outcome | 7 | 126, 186, 257, 439, 440, 441, 473 |
| Scope: fraud, non-violent, or not crypto-linked | 16 | 8, 18, 27, 39, 42, 56, 61, 73, 83, 89, 94, 137, 150, 260, 394, 398 |
| Other | 470 | 1, 3, 4, 5, 7, 8, 9, 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 32, 33, 34, 35, 39, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 84, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 114, 116, 117, 118, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 156, 157, 161, 164, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 188, 189, 190, 193, 194, 195, 196, 197, 199, 200, 201, 202, 203, 205, 206, 207, 208, 209, 210, 211, 215, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 384, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 444, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 471, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487 |
| Multiple victims, proxy victims or one victim field | 10 | 23, 24, 26, 39, 74, 387, 401, 404, 427, 431 |
| Amount and coin fields cannot split crypto from cash, goods or fiat | 20 | 4, 7, 9, 21, 25, 61, 118, 123, 128, 181, 188, 254, 255, 357, 384, 407, 412, 465, 471, 486 |
| Control moves between places; one venue field | 5 | 5, 401, 412, 444, 460 |
| Outcome after the transfer (killing, escape, rescue) is not an initiation label | 9 | 52, 84, 147, 166, 201, 361, 366, 432, 458 |
| Crypto link or complainant account is itself unverified | 7 | 96, 175, 178, 199, 399, 400, 443 |
| Initiation or entry method not reported | 7 | 141, 156, 223, 409, 454, 477, 485 |
| Remote operator, phone drained after the event, or company infrastructure | 4 | 28, 164, 196, 211 |
| Other | 408 | 1, 3, 4, 5, 7, 8, 11, 12, 13, 14, 15, 16, 18, 19, 20, 22, 23, 24, 25, 27, 28, 29, 30, 32, 33, 34, 35, 40, 41, 42, 43, 44, 45, 46, 48, 49, 50, 52, 53, 55, 56, 59, 60, 61, 63, 64, 66, 67, 68, 69, 70, 71, 72, 73, 74, 76, 77, 78, 79, 80, 81, 82, 85, 86, 88, 89, 90, 91, 92, 93, 96, 99, 102, 103, 104, 105, 106, 108, 109, 110, 111, 113, 114, 116, 117, 118, 121, 122, 123, 124, 126, 128, 130, 134, 136, 137, 138, 141, 142, 143, 144, 145, 147, 151, 152, 153, 154, 157, 161, 166, 167, 168, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 182, 183, 188, 189, 190, 193, 194, 195, 197, 199, 200, 202, 203, 205, 206, 207, 208, 209, 210, 215, 223, 254, 255, 258, 259, 260, 318, 352, 357, 358, 360, 361, 363, 366, 373, 374, 375, 376, 377, 379, 380, 381, 382, 383, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 397, 398, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 413, 414, 415, 416, 417, 418, 419, 421, 422, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 442, 443, 445, 447, 449, 450, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 469, 470, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487 |
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).
@@ -473,6 +480,89 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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)
### Multiple victims, proxy victims or one victim field
- 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: 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 26: two victims held together, and the schema has one victim field
- case 39: the broker Mr Pang brought with him was assaulted too, and the schema has one victim field
- case 74: two victims held in two places by one gang cannot be carried by a single label
- 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 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 404: three victims in one household are held in one victim field
- case 427: the target was absent and the household was held in his place; the labels do not mark proxy victims
- case 431: the holder was absent and his family was held in his place; the labels do not mark proxy victims
### Amount and coin fields cannot split crypto from cash, goods or fiat
- case 4: money_wanted cannot show that only $8,500 of the $12,000 was cryptocurrency and $3,500 was cash
- 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 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 21: the loss was hardware whose value keeps generating income for the thieves; the amount fields cannot express that
- 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 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 118: the target was a crypto consultant and the loss was two watches; the labels do not distinguish an attack on a crypto figure whose crypto was never touched
- case 123: no cryptocurrency was demanded or taken; the record's own coin_type reads Watch
- case 128: nothing crypto was taken - the loss was watches, a ring and cash - so the case sits in this database on the motive alone
- case 181: a crypto trader robbed of phones, watches, a card and cash with no crypto reported taken does not fit the database's crypto-loss framing
- case 188: the record's crypto figure belongs to a separate online theft a week earlier, not to this attack, and the schema has one amount field
- case 254: a demand of 500 BTC against a take of about $600,000 has one amount field, and the record used it for the take
- case 255: the loss runs from at least $72,000 in the charging documents to $8 million in the prosecutors' statement, and there is one amount field
- case 357: the £450,000 watch was the larger single loss and no field separates it from the crypto
- case 384: no cryptocurrency was taken — the loss was 1 billion yen in banknotes and the crypto nexus is the victims' employer's line of business, which coin_type can only record as '4 briefcases with cash'
- case 407: a ransom paid in part and a victim killed anyway has no field; the record's money_wanted carries both numbers in prose
- case 412: a theft of physical goods (silver) alongside the crypto has no field of its own; the record puts it in coin_type
- case 465: the £250,000 covers a watch and bitcoin together; the amount fields cannot express a combined loss
- case 471: the record's 'remote mastermind' watching the Snapchat stream appears in no article on file
- case 486: the record cannot hold the split between the crypto ($562,155) and the jewellery (about $413,500)
### Control moves between places; one venue field
- case 5: control shifted from a street corner to the buyer's car, which a single label cannot show
- 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 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 444: a victim held in a stationary van in woodland is neither a premises nor a vehicle in motion
- 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
### Outcome after the transfer (killing, escape, rescue) is not an initiation label
- case 52: the victim's own escape by jumping from a second-floor balcony, and the injury risk he took, has no field
- case 84: armed self-defence by the victim, and the fact that the only firearm was his, has no field
- case 147: Dodged Attack does not express the harm that did occur: the concierge was gagged and tied before the attack was interrupted
- case 166: one victim was airlifted to hospital, which no outcome value among released / escaped / rescued / killed / foiled / unharmed names
- 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 361: no field records that the attempt was broken by police already at the scene rather than by anything the victims did
- case 366: the victim was killed after the wallets were emptied, which the initiation-based labels do not express
- case 432: a rescued victim who turns out to be wanted himself has no place in the schema
- case 458: a transfer interrupted mid-execution is neither completed theft nor an attempt in the flag set
### Crypto link or complainant account is itself unverified
- case 96: a killing whose motive is inferred from the victim's public profile sits at the edge of the crypto-attack frame
- 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 178: the crypto connection here is the ransom currency alone — the reports do not say the family were crypto holders
- case 199: a case in which police end up doubting the complainant has no way to be marked
- 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 443: a case where the crypto connection is the son's wealth rather than the victim's own holdings is not expressible
### Initiation or entry method not reported
- case 141: how he was lured into the vehicle is not described
- case 156: how the two got inside is not reported, so the initiation method has no label
- case 223: the record's initiation - a woman used to lure the businessman to a house - appears in no article on file, so the label rests on the police account of a house in Meycauayan
- case 409: no source gives a venue, and Home Invasion, Kidnapping and Armed Robbery all turn on where control was taken, so none of the eleven labels can be supported
- case 454: the record's "garage" is not in the file, which says only a room
- 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 485: the file cannot say whether the business meeting at the fuel depot was the lure
### Remote operator, phone drained after the event, or company infrastructure
- 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 164: a raid whose object was the company's servers rather than one holder's wallet has no label
- 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 211: the attackers operated the victims' phones themselves while a third party coached them by telephone; no label expresses the remote-operator role
### 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
@@ -481,17 +571,13 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -507,21 +593,15 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -534,7 +614,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -550,7 +629,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -559,7 +637,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -580,7 +657,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -594,7 +670,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -605,7 +680,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -627,17 +701,14 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -645,14 +716,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -661,12 +730,9 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 153: a robbery staged by the hosts on themselves, so that the victim reports it as a crime against all of them, has no label
- case 154: an attack commissioned and paid for by aggrieved investors has no label
- case 154: the killing is the outcome of this case rather than a label of its own
- case 156: 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
@@ -682,36 +748,29 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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 177: how the attackers learned his address and that he held crypto is the question the case turns on, and no field holds it
- case 177: the record gives no duration and neither does the article
- case 177: the whole case rests on the victim's own posts relayed by one outlet, with no police or court source, and no field records that
- case 178: the crypto connection here is the ransom currency alone — the reports do not say the family were crypto holders
- case 178: the victim is a child and the ransom target is someone else; the labels have no way to separate the person held from the person extorted
- case 179: extortion leveraging the victim's own illegal earnings ('he was afraid I would file a complaint') is not expressible
- 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 188: a kidnapping that lasted from one crash to the next, minutes rather than hours, reads the same in the labels as a week-long captivity
- case 188: the people held were leverage against their son, and no field records that the target was someone else
- case 188: the record's crypto figure belongs to a separate online theft a week earlier, not to this attack, and the schema has one amount field
- case 189: an attack that landed an assault but failed at the theft sits between Dodged Attack and a completed robbery; the labels force a choice
- case 190: the record's single Home Invasion label loses the five days of captivity at two other addresses
- case 193: neither source says where he was held or for how long, so Express Kidnapping can be neither ruled in nor out
- 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 203: the extortion target was the son abroad, not any of the people held, and no field records that
- case 203: the two articles disagree on whether the partner was taken in the car or left tied at the house, and the victim field cannot hold the doubt
@@ -722,15 +781,11 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 209: a ransom paid, then frozen and seized, is a theft that was largely undone, and the theft flag cannot say so
- case 209: the extortion target was a third party, another Ledger co-founder, not either of the people held
- case 210: the file does not say whether the house where he was held was the meeting place itself or somewhere he was taken to; Kidnapping is used for captivity on premises that are not his
- case 211: the attackers operated the victims' phones themselves while a third party coached them by telephone; no label expresses the remote-operator role
- case 215: a killing during a trade in a hotel room; Armed Robbery is the label for weapon-plus-theft, with the P2P trade as the initiation
- case 223: a ransom paid twice and the hostages killed anyway has no field; the outcome column can only say killed
- case 223: the record's initiation - a woman used to lure the businessman to a house - appears in no article on file, so the label rests on the police account of a house in Meycauayan
- case 254: a demand of 500 BTC against a take of about $600,000 has one amount field, and the record used it for the take
- case 254: the laundering leg through HTX and Kyrrex has no field
- case 255: a remote third party feeding account information to the men in the house by phone has no field
- case 255: the husband was driven three hours to a second property and forced to transfer there, a kidnapping leg inside a home invasion that one scenario field cannot carry
- case 255: the loss runs from at least $72,000 in the charging documents to $8 million in the prosecutors' statement, and there is one amount field
- case 258: police say there were at least five participants and only three are accounted for
- case 258: the cash loss of 14,600 euros and the crypto loss of more than 83,000 dollars sit in one money field, and the record carries only the crypto
- case 258: the victim was handling other people's funds, which is the reason police give for his being targeted, and no field records it
@@ -743,18 +798,15 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- case 352: a man killed while resisting and one of the attackers killed by a defender sit together in a single life_taken count of 2
- case 352: a third person, the brother-in-law who came with a gun, was shot and wounded and no field records him
- case 357: the two reports disagree on whether the victims or the robbers were the ones left in Five Mile Drive, and no field records that
- case 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
@@ -770,9 +822,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -789,29 +839,22 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -819,8 +862,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -841,15 +882,12 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -868,9 +906,7 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -880,20 +916,17 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -903,13 +936,11 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -918,7 +949,6 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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
@@ -939,10 +969,8 @@ Proposed additions to the vocabulary, in order of how often the gap appears: (1)
- 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