feat(verify): batch 14 verified (60-51)

Writer agent from the dossiers; checker flagged one attribution on 58, fixed.
57 is Canada not USA; 56 and 52 v1 labels unsupported; 54 theft and weapons
contradicted by police; 58 detention unconfirmed (Hagen).

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 11:25:27 +02:00
co-authored by Claude Fable 5.1
parent 185cfe9286
commit 13d9882813
17 changed files with 1865 additions and 803 deletions
+74
View File
@@ -0,0 +1,74 @@
# Batch 14 — contradictions, flag proposals and notes for Sofia (2026-09-30)
## case 60
- **location** — record: Trader lured to apartment | article (LancsLive): the meeting was rearranged 'for the Winckley Square apartments', but the same report then calls the place 'the hotel room' and 'a hotel bathroom' and 'Back at the hotel'
- **attackers** — record: (no attacker count or names on the record) | article (LancsLive): 'Tasmina Rhaman, 21' in one paragraph and 'Rahman' in every later paragraph, for the same person
- label gaps: 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); 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; a child victim and child offenders have no field
- note: The record's date is 'January ?, 2020'; the article dates the attack to Sunday 16 January 2020, so the day can be filled in. money_wanted is null on the record and the article gives 20,000 pounds demanded against a 10,000 pound withdrawal limit; coin_type is null and the article names no coin. held_duration left null because the file never says how long he was held or how long the drive lasted, although the sequence of events (the trip to his home and the drive to Chorley) suggests more than minutes - your call. venue_of_control set to the apartment because control was gained and the extortion executed there; the car boot leg would read as vehicle in motion.
## case 59
- **amount** — record: money_wanted $10.000, coin_type BTC | article (Vanguard): the $10,000 is the sum the suspects expected to find, per their confessional statements, not a sum demanded from the victim: 'were disappointed to find out that what was left when they struck was $400'
- **attackers** — record: (no count on the record) | article (Vanguard): 'eight members of the Vikings confraternity were fingered in the incident', of whom four were arrested
- label gaps: 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; a killing that happened because the victim recognised the attackers, rather than to coerce him, has no field
- note: Two copies of the same police-source account are on file: the Vanguard piece (linked) and a HeraldSheets rewrite that credits Punch; the quoted passages are identical, so nothing is corroborated independently. The HeraldSheets piece ends with the outlet's own safety advice to crypto holders, which is not case information and was not used. The record's date 'January ?, 2020' fits the Vanguard wording 'last month' in a February 2020 report; the day is not recoverable from this file. arrests recorded as 'some' because four of the eight named by police were in custody.
## case 58
- **location** — record: Oslo, Norway | article (The Guardian): 'went missing from their home in Lorenskog, near Oslo' / 'in Lorenskog, about 12 miles (20km) from Oslo'
- **amount** — record: money_wanted 9m euros, coin_type MNR | article (The Guardian / Verdens Gang): 'The Verdens Gang daily reported that the presumed abductors had demanded 9m euros (8m pounds) in the cryptocurrency Monero ... Police at the time refused to confirm the sum'
- **detention** — record: kidnappings = 1 | article (The Guardian): 'Online contacts with the presumed kidnappers earlier in the investigation were unable to confirm that those people were holding Hagen, 68, or that she was still alive'
- **attackers** — record: (none) | article (The Guardian (26 June 2019), The Guardian (9 January 2019)): Tom Hagen's fortune is given as 'an estimated fortune of 174m euros' in the June 2019 piece and as '1.7bn kroner (156m pounds)' in the January 2019 piece
- flag `kidnappings` = 1 -> propose **unconfirmed**: 'Online contacts with the presumed kidnappers earlier in the investigation were unable to confirm that those people were holding Hagen, 68, or that she was still alive'; police's modified hypothesis was that the kidnapping may have been staged
- flag `violence_torture` = 1 -> propose **unconfirmed**: no assault, injury or ill-treatment is described anywhere in the file
- label gaps: 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; the labels cannot express a case where the crime itself is undetermined
- note: The file never reports a body, a confirmed death or any arrest - life_taken rests on the lead investigator's stated hypothesis, so the summary keeps his wording. Detention and violence_torture are proposed as 'unconfirmed' rather than 0 because the file leaves open what happened to her, and 0 would assert more than the sources do. The record's 'not in lopps list' note and has_processed_date 0 suggest this record was never worked; the two Guardian pieces on file are eight months apart and the later one supersedes the earlier on the central question. Whether a case with no established captivity and no proven crypto payment belongs in a K&R database at all is your call.
## case 57
- **location** — record: country USA, location Vernon, British Columbia | article (Castanet): 'anyone with information can call Vernon North Okanagan RCMP' - the RCMP and British Columbia place this in Canada, not the USA
- **scenario** — record: Armed Robbery in Public Space | article (Castanet): 'Two masked men broke into Simply Delicious Food Market and ran off with cash stolen from a bitcoin ATM. The robbery happened at about 4 a.m.' - no weapon and no person present
- **date** — record: November 19, 2019 | article (Castanet): 'The robbery happened at about 4 a.m. Tuesday morning' - the article gives the weekday only
- label gaps: 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); the target was crypto infrastructure and its cash float, not a holder's wallet
- note: The country field is wrong: Vernon is in British Columbia and the appeal is to the Vernon North Okanagan RCMP, so this is Canada. Outcome left null because none of the six values fits a theft with no person in it, the same treatment as 198 and 112. Only one source is on file and the linked URL is a Castanet click-counter redirect which was refused on the raw request, so there is no second copy of the text; the record also credits 'YT' for a video that is not in this file.
## case 56
- **scenario** — record: Kidnapping | article (NDTV): 'They arrived in Dehradun, where Shakoor had been living in a rented house, and pressured him for the password' - the torture happened where he lived; the only journey described is his killers taking him to two hospitals afterwards
- **weapons** — record: weapons = 1 | article (NDTV): 'beaten to death by five of his associates' - no weapon is named
- **description** — record: notes: 'after pretending his wallet with company funds got hacked' | article (NDTV): 'Shakoor allegedly told them that his bitcoin account had been hacked' - the report keeps this as an allegation and does not say he was pretending
- **date** — record: August 26, 2019 | article (NDTV): the report gives weekdays only: the body was left at the hospital 'on Thursday night' and the five were arrested 'on Friday'
- flag `weapons` = 1 -> propose **0**: no weapon is named anywhere in the report; he 'was beaten to death by five of his associates'
- label gaps: 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; extortion of an account password, rather than of a holder's funds, has no field
- note: Two copies of the same NDTV report are on file (the sheet text and a Wayback snapshot of the live page) and they match. The named men - Ashique, Arshad, Yasin, Rehaab and Muneef - are the five aides police were still looking for, not the five arrested; the arrested five are unnamed. This record sits oddly in a K&R database of attacks on crypto holders: the victim was the alleged operator of a Rs 485 crore investment fraud and the attackers were his own associates chasing money they had collected from investors. Flag it for an inclusion decision.
## case 55
- **weapons** — record: notes: 'armed with pistol' | article (ORF Oberoesterreich): 'Armed with a pistol and a rubber truncheon' - the record omits the truncheon
- label gaps: 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; the victim was left bound and had to free himself, which none of the outcome values names precisely
- note: auto-trim-review.md lists this page as a WEAK anchor (one case-term hit), but it is the right page: the German original on ooe.orf.at matches the sheet's English rendering line for line - Wels, a 30-year-old, his office, the pistol and rubber truncheon, the cable and duct tape. Outcome recorded as 'escaped' because the attackers left him tied up and he freed himself; 'released' would also be arguable. held_duration left null - the file never says how long the raid lasted or how long he was bound before freeing himself. money_wanted reads 'unknown', which matches the article ('The amount is not yet known'); a later follow-up report would be worth chasing for the sum.
## case 54
- **theft** — record: theft = 1 | article (Cointelegraph): 'West Midlands Police has launched an investigation, but have confirmed that nothing of value was stolen from the business'
- **weapons** — record: weapons = 1 | article (Cointelegraph / Daily Mail): 'the thieves had attempted to steal a Bitcoin ATM using a rope attached to their car' - no weapon is described
- **description** — record: 'Masked raiders hold up Bitcoin Exchange in front of dozens of witnesses'; notes: 'cash from ATMs' | article (Cointelegraph): the footage shows 'the burglars ransacking the building' and the gang speeding away; nothing of value was taken, and the cash motive is the owner's belief, not a police finding
- **location** — record: Sparkhill, Birmingham, England | article (Cointelegraph): the report places the exchange only in 'the English city of Birmingham' and names no district
- flag `weapons` = 1 -> propose **0**: no weapon is reported; the only tool described is 'a rope attached to their car'
- flag `theft` = 1 -> propose **0**: 'West Midlands Police has launched an investigation, but have confirmed that nothing of value was stolen from the business'
- label gaps: 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); the machine and its cash float, not a holder's wallet, were the target - an attack on crypto infrastructure has no label
- note: One source only, in two copies (the sheet text and a Wayback snapshot of the Cointelegraph page dated 2026-02-07); they match. The Cointelegraph URL slug reads 'bitcoin-embassy' while the headline and body say 'Bitcoin exchange' - worth resolving which business this was, since the record's victim field is the generic 'Bitcoin Exchange'. The article's last sentence, about a Bitcoin trader attacked at home in February by robbers disguised as police, is a different incident and was not used. Everything factual here beyond the police line comes from Cointelegraph relaying the Daily Mail, which is not on file.
## case 53
- **date** — record: June 30, 2019 | article (Newsweek): the report gives no calendar date: the ordeal 'lasted more than two weeks', ended 'yesterday', and the police operation was 'on Sunday'
- **description** — record: notes: 'two weeks in high rise building' | article (Newsweek): the same report gives both 'the ordeal - which lasted more than two weeks' and 'held captive for 15 days inside a high-rise building'
- **amount** — record: money_wanted (null), coin_type (null) | article (Newsweek / Hindustan Times): 'demanded 80 bitcoin worth 8 crore rupees ($1.2 million) ... The gang demanded 10 lakh rupees ($15,000) from his family members'
- label gaps: 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; three victims taken on two different days in one operation cannot be expressed; two different ransom demands in one case, one in bitcoin and one in rupees, have no field
- note: One source only, in two copies (the sheet text and the fetched Newsweek page); they match. Newsweek is relaying the Hindustan Times and NDTV, so nothing here is independently reported. The closing passage about a 13-year-old boy kidnapped in South Africa is a different case and was not used. money_wanted and coin_type are empty on the record although police gave two figures - 80 BTC ($1.2 million) and 10 lakh rupees ($15,000); the record needs both, or a decision on which to carry. arrests recorded as 'some' because seven were arrested and the report does not say the gang is fully accounted for.
## case 52
- **scenario** — record: Home Invasion | article (TV 2): 'The robber forced his way into the apartment and said, "Get down, or I'll shoot" ... The robber did not get any valuables because the millionaire managed to escape' - entry was forced but no occupant was held and nothing was taken
- label gaps: 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; the victim's own escape by jumping from a second-floor balcony, and the injury risk he took, has no field; no cryptocurrency was demanded in this file, so the case is in the database on the strength of who the victim is
- note: One source only, in two copies (the sheet's English rendering and the fetched Norwegian page); the Norwegian original matches, including the picture caption 'He got away without giving up any valuables'. Outcome recorded as 'escaped' rather than 'foiled' because the file turns on the victim's own escape. arrests set to 'some': the file reports charges filed by the Oslo Public Prosecutor's Office and a court date for one accused, but never says he was arrested and reports no conviction. Note that no cryptocurrency demand appears anywhere in this file - the crypto link is the victim's profile, which is worth recording if the case stays in.
## case 51
- **weapons** — record: weapons = 0, while the record's own notes read 'they threatened the employees with a machete' | article (Northampton Chronicle & Echo): 'one threatened staff with a curved machete while the other smashed a Bitcoin machine off the shop wall with a sledgehammer'
- **victim** — record: victim 'Costcutters' | article (Northampton Chronicle & Echo): 'the Costcutter shop on St Leonard's Road' - Article 1 says staff were threatened, Article 2 says 'Robbers in Northampton threatened a shopkeeper with a machete'
- flag `weapons` = 0 -> propose **1**: 'one threatened staff with a curved machete while the other smashed a Bitcoin machine off the shop wall with a sledgehammer'
- label gaps: 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; a weapon used to hold staff off while a machine is ripped from the wall sits between Armed Robbery and a straight burglary
- note: The weapons flag contradicts the record's own notes field, which already records the machete - a clean 0 to 1 correction. Detention is borderline and your call: staff were held off at machete point inside the shop for as long as it took to break the machine loose, which the flag legend could read as held, but nothing was done to keep them there and the men walked out, which is rule 3. Written as no detention, record 0 kept; venue_of_control is recorded as the staff's workplace because that is where the machete was used, even though nobody was held. Three copies of one report are on file (Article 1, Article 2 and the fetched page) and they agree; Article 2 carries two unrelated headline teasers from the site's sidebar, which were ignored.