This repository has been archived on 2026-10-19. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
DB-cleanup/merge-output/batches/contradictions-28.md
T
StellarCrowandClaude Fable 5.1 0046fa13ac feat(verify): batch 28 verified (402-393)
Writer agent from the dossiers; checker flagged two attribution overstatements
on 394, fixed. 399 record-only (direct victim report); 402, 401, 397 v1
labels unsupported; 400's crypto link rests on an unconfirmed ransom note.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GZZENdTLzNGsbNy4DyF1yt
2026-09-30 11:58:29 +02:00

95 lines
23 KiB
Markdown

# Batch 28 — contradictions, flag proposals and notes for Sofia (2026-09-30)
## case 402
- **victim** — record: Two adults | article (Yahoo / The Tribune): a third victim - the one who called 911 and did not make contact with the intruders - hid in the back of the home
- **scenario** — record: Authority Misuse | article (Yahoo / The Tribune): two people arrived at the home with a box and a dolly, claiming to be delivery drivers
- **description** — record: posed as FedEx drivers | article (Yahoo / The Tribune): duct tape, zip ties, a moving dolly and UPS-style clothing littering the home and backyard ... One suspect had previously purchased FedEx-style uniforms
- **notes** — record: assaulted them demanding wallet access | article (Yahoo / The Tribune): In his interview, Lapaille denied assaulting the victims and didn't mention a gun
- **notes** — record: Recruited/extorted via Signal app by unknown handlers ("Red" and "8") | article (Yahoo / The Tribune): LaPaille apparently told police in an interview following his arrest that the two boys had met recently and had been extorted over the Signal app by two subjects known as 'Red' and '8'
- **notes** — record: They restrained the two adults with duct tape | article (Yahoo / The Tribune): restrained the residents using duct tape (documents) while zip ties are listed only among the items police observed in the home and backyard
- flag `weapons` = null -> propose **1**: 'a 3D-printed gun that was not loaded with ammunition'; police said they did not know if the gun worked
- label gaps: 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; 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
- note: Scenario should move from Authority Misuse to Home Invasion, and weapons from null to 1 (3D-printed gun at the scene, unloaded, working state unknown). The record's victim count misses the third person in the house who called 911. url_3 (bitcoinethereumnews.com) is recorded BLOCKED with no text on file, so nothing rests on it. Two record/AI-summary details have no support in any block on file: that the victims were restrained with zip ties as well as duct tape (zip ties were only observed lying around), and that the mother specifically tipped police (the Tribune says 'a parent', Gizmodo says 'one of the teens' mothers'). Arrests marked 'some' because the two who entered were arrested while 'Red' and '8' were not identified.
## case 401
- **date** — record: date February 5, 2026; original_date February 4, 2026 | article (Le Monde, Le Dauphiné Libéré): At around 3 am on Thursday, an unknown number of individuals broke into one of the victims' homes (Le Monde); 'enlevée dans la nuit de mercredi à jeudi' (Le Dauphiné Libéré)
- **status** — record: They were released after 30 hours with injuries | article (Le Monde): A passerby heard banging coming from behind a garage door ... and was able to free two women
- **duration** — record: 30 hours | article (Le Monde, Le Dauphiné Libéré): after an ordeal that lasted more than 24 hours (Le Monde) against 'libérées 30 heures plus tard' in Le Dauphiné Libéré's headline
- flag `drugs_alcohol` = null -> propose **0**: nothing on the subject in either article
- flag `weapons` = null -> propose **unconfirmed**: no weapon is mentioned; neither article describes the entry or how the women were guarded
- flag `theft` = null -> propose **0**: nothing is reported taken; Le Monde says the detention was 'likely in connection with a ransom demand' and neither article says anything was paid
- label gaps: 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; 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
- note: Two wording fixes: they were not released, a passerby freed them; and original_date 4 February does not match a 3 a.m. Thursday 5 February break-in. held_duration set to 'hours' although about 30 hours straddles the hours/days boundary - rule it either way and the value is defensible. Both blocks are cut very hard (Le Dauphine kept 1 paragraph of 51, Le Monde 4 of 11, and the Le Monde block carries a subscription notice), so a re-fetch would probably add a great deal. The file's AI summary carries much that neither block supports - three attackers, a broken front door, blows to the face, blood stains at the scene, the transfer to JIRS Lyon, the partner being co-founder of a startup acquired in 2024 by a North American platform - none of that should reach the record from here. The record's notes field is a verbatim copy of Le Monde's opening sentence.
## case 400
- **date / timeframe** — record: abducted ... between 9:30 PM January 31 and ~2 AM February 1, 2026; notes: pacemaker stopped syncing with Apple Watch at ~2 AM February 1 | article (TMZ): PCSD says they haven't released any specific timeframes related to the pacemaker and are 'working to review any available data that may assist in this investigation'
- **scenario / motive** — record: scenario Kidnapping with money_wanted '"millions" in Bitcoin' | article (cleveland.com / Associated Press): Investigators do not believe at this point that the abduction was part of a robbery, home invasion or kidnapping-for-ransom plot, the person said
- **money_wanted** — record: "millions" in Bitcoin | article (Decrypt): Law enforcement has not confirmed whether they believe the ransom note is actually from the kidnappers or a hoax to steal Bitcoin
- **notes** — record: blood trail from entryway to driveway | article (Raw Story / NewsNation): The blood was visible outside the front entrance of the rural Tucson home after authorities cleared the crime scene ... It wasn't immediately clear whose blood was inside the house
- **description** — record: (no mention of what the note said she was wearing) | article (TMZ, Decrypt): TMZ: 'Harvey and Charles said she was wearing an item mentioned in the note. In fact, the note says she was not wearing it' against Decrypt: 'The note also included a description of what Guthrie was wearing at the time'
- flag `drugs_alcohol` = null -> propose **0**: nothing on the subject in any article on file
- flag `weapons` = null -> propose **unconfirmed**: no weapon is mentioned in any article on file; the manner of the abduction is not described
- label gaps: 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; 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
- note: The case's place in a crypto database is the open question: the only crypto element is a ransom note of unconfirmed authenticity sent to TMZ (and a second to KOLD), and the AP's source says investigators do not believe this was a kidnapping-for-ransom plot. Consider a disputed or unconfirmed-motive bucket rather than deleting or keeping it silently. The record's 9:30 p.m. drop-off by a son-in-law and the ~2 a.m. pacemaker cut-off have no support in any article on file and PCSD says it has released no pacemaker timeframes; 'DNA confirmed as Nancy's' appears only in the file's AI summary and Raw Story says the opposite. All five blocks are dated 3 February 2026, so the status is five days old at most relative to the record - it needs a refresh before publication. theft 0 is right for her belongings, but cameras including a Ring doorbell were removed from the property.
## case 399
- flag `kidnappings` = 1 -> propose **unverified**: no article or statement on file; the record is the only text
- flag `violence_torture` = 1 -> propose **unverified**: no article or statement on file; the record is the only text
- flag `drugs_alcohol` = 0 -> propose **unverified**: no article or statement on file; the record is the only text
- flag `weapons` = 1 -> propose **unverified**: no article or statement on file; the record's description says 'ambush' but names no weapon
- flag `theft` = 1 -> propose **unverified**: no article on file; the record says he lost all his crypto savings and gives $750,000, with no breakdown
- flag `life_taken` = 0 -> propose **unverified**: no article or statement on file; the record is the only text
- label gaps: 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); 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
- note: Record-only, and unlike 11, 45 and 66 this is not a sourcing failure: the case was reported directly to Gart Research by the victim, so the primary source is a person, not a page. The action is therefore not to re-source the web but to get the victim's account written into the dossier as a dated statement (with whatever consent and anonymisation he wants), after which the six flags and the label can be verified in the normal way. Until that exists, the six flags are marked unverified because there is nothing on file to test them against, not because the values look wrong - detention, violence, a weapon and a $750,000 loss are all plausible for the incident the record describes. The file's AI summary contains a long narrative (a blocked bank transfer, a Telegram trading group, a first aborted meeting at a restaurant, strangulation with a towel, both phones unlocked, a change of clothes and being driven off in his own car and abandoned) that is bulk-import text with no source behind it in this file; it reads like a retelling of the victim's report and would be the obvious thing to confirm with him line by line, but none of it can be published as verified as things stand.
## case 398
- **amount** — record: 11,000 Litecoin worth Rs 9.64 crore ($1.5 million) | article (The Hindu): The builder and his accomplices had also transferred another 166 bitcoins worth Rs 9.64 crore into their account
- **amount** — record: 2,256 Bitcoin worth Rs 131.07 crore | article (India Today): The accused allegedly extorted 2,254 Bitcoins, 11,000 Litecoins and Rs 14.5 crore in cash in exchange for the release of one of the victims
- **description / notes** — record: BitConnect's developer and administrator who allegedly possessed access to over 25,000 Bitcoin | article (The Hindu, India Today): Bhatt's men kidnapped Dhaval Mavani at gun-point, as the latter was also attached with the bankrupt firm - no role and no 25,000 bitcoin figure appears in either article
- **attackers** — record: Shailesh Babulal Bhatt (mastermind) and 9 accomplices | article (The Hindu, India Today): neither article gives a number of accomplices; The Hindu names only Nikunj Bhatt and India Today only Nikunj Bhatt and Sanjay Kotadia
- flag `violence_torture` = 1 -> propose **threat only**: the only force described against Mavani is the gunpoint kidnapping and the forced transfers; no assault or injury of his appears in either article
- flag `drugs_alcohol` = null -> propose **0**: nothing on the subject in either article
- label gaps: 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; 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)
- note: 397 and 398 are the same operation by the same group, and the CID narrative that would support 397's Authority Misuse label (posing as Income Tax officials, the farmhouse, three days at gunpoint, the Rs 34.5 lakh silence payment) sits in this file, in The Hindu, not in 397's - linking that article on 397 as well would fix that record in one move. Record claims with no support in this file: the 25,000 Bitcoin access, the developer/administrator role, the farmhouse, a 1-4 February captivity, the warning never to return to Gujarat, the UAE deportation and the FBI inquiry (all of that is in the file's AI summary only). The Rs 9.64 crore tranche needs a ruling: The Hindu calls it 166 bitcoins, India Today 11,000 Litecoins, and the record follows India Today. The bitcoin count for the main transfer is 2,256 in The Hindu and the record, 2,254 in India Today. violence_torture is dropped to threat-only because nothing on file describes Mavani being beaten - the beating in The Hindu is Bhatt's own, by the Amreli police, which is a different case in the same web.
## case 397
- **duration** — record: They held him at a farmhouse in Surat at gunpoint for three days | article (New Indian Express): kidnapped one Piyush Savalia ... on January 30 released two days later
- **scenario / description** — record: abducted Piyush Savaliya ... by posing as Income Tax Department officers | article (New Indian Express, CoinJournal): neither article on file mentions any impersonation of officials, or any farmhouse
- **theft** — record: theft = 0 | article (CoinJournal): deceived BitConnect investor Shailesh Bahtt allegedly extorted cryptocurrencies and cash worth over Rs 155 crore (US$22 million) at gunpoint from Dhaval Mavani and Piyush Savaliya of BitConnect
- **notes** — record: Bhatt paid him Rs 34.5 lakh for silence and a false statement denying that any kidnapping occurred | article (New Indian Express, CoinJournal): neither article on file mentions the payment or the false statement
- **attackers** — record: Shailesh Bhatt and nine accomplices | article (New Indian Express, CoinJournal): neither article gives a number of accomplices
- flag `violence_torture` = null -> propose **0**: no assault or injury is described in either article; the only force on file is the gunpoint threat
- flag `drugs_alcohol` = null -> propose **0**: nothing on the subject in either article
- label gaps: the impersonation of Income Tax officers that the record's Authority Misuse label rests on appears nowhere in this case's file; 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
- note: This record is sourced worse than its twin. Everything that makes it distinctive - the Income Tax impersonation, the farmhouse, three days at gunpoint, nine named accomplices, the Rs 34.5 lakh silence payment - is absent from both pages on file; all of it is in The Hindu's CID account, which is linked on 398 instead. Add that link here and 397 becomes verifiable; until then Authority Misuse has nothing behind it and the scenario should not be published as certain. Note also that the reports field says New Indian Express, but the New Indian Express page on file is a Congress press-conference story about the wider Gujarat bitcoin affair, not a report on this kidnapping, and CoinJournal's page is about the arrest of BitConnect's India head - both were used only for the one passage each about this case. venue_of_control left null because the farmhouse is the record's word, not any article's here; held_duration 'days' follows the two days Gohil described, which is itself one day short of the record.
## case 396
- **money_wanted** — record: (null) - description says 'Ransom demanded, amount unknown' | article (Le Dauphiné Libéré): Une rançon de 3 millions d'euros en cryptomonnaies a également été demandée
- **victim** — record: notes: 'the 70-year-old man was freed in the early hours of Monday morning' | article (Le Dauphiné Libéré): Un homme âgé de 74 ans a été enlevé - the article's headline and body both say 74, while the URL slug says 70
- **status** — record: freed in the early hours of Monday morning | article (Le Dauphiné Libéré): le septuagénaire a été libéré dans la nuit de dimanche à lundi, un peu avant minuit
- flag `drugs_alcohol` = null -> propose **0**: nothing on the subject in the article
- flag `weapons` = null -> propose **unconfirmed**: no weapon is mentioned; the article does not describe the abduction itself
- label gaps: 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
- note: Two easy fixes: money_wanted should read 3,000,000 EUR in cryptocurrency (the headline states it), and the notes line saying 70-year-old should read 74 - the 70 comes from the URL slug, which Le Dauphiné evidently corrected after publishing. Freed a little before midnight on the Sunday night, not in the early hours of Monday. venue_of_control left null: the article says where he was taken from and where he was freed, never where he was held. The kept block is paragraphs 20-23 of 42, so the file's AI summary details that are missing here (about 18 hours of captivity, a reference to similar cases involving mutilation) may well be in the dropped paragraphs - worth a fuller extract from staging before the case is published.
## case 395
- **attackers** — record: Two men kidnapped a teenager after school | article (Nice-Matin): Dix jours plus tard, la BRI ... interpelle plusieurs individus. Mineurs, ils demeurent libres, sous contrôle judiciaire, en attendant leur procès
- label gaps: 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; 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
- note: Arthur is a pseudonym - the article states that the first name was changed for safety - so the victim field should stay '17-year-old' and the name should not enter the database. venue_of_control is the least comfortable field here: he was held on a landing about ten floors up in his own residential building, which is neither his flat nor a public street; I have put victim's private space as the nearest of the six, but a reviewer could fairly read it as public space. held_duration left null because the article never says how long the encounter lasted, only what happened in it. The block is auto-trimmed and unreviewed (paragraphs 0-17 of 43), and I read it through: it is one continuous account of this case with no other case in it, so the trim is safe to use. Two follow-on events may deserve their own treatment rather than being buried in this record's status: the forced lock and the petrol-on-the-door video sent while the family was abroad.
## case 394
- **victim** — record: "Maxence" | article (ActuCrypto, Journal du Coin): Trois jeunes hommes d'une vingtaine d'années ont reconnu leur cible, soi disant prénommée Maxence - a reported first name, not a confirmed identity
- **scenario** — record: Express Kidnapping | article (ActuCrypto): Il ne s'agit pas d'une demande de rançon classique, mais d'une expédition punitive - no payment, withdrawal or transfer during the detention is reported in either article
- flag `weapons` = null -> propose **0**: no weapon is mentioned in either article
- label gaps: 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; nothing in the schema marks a case in which the database's victim is himself the alleged offender
- note: Both blocks are crypto-media retellings of a Le Bien Public report; the primary is not on file, so every detail here is second-hand and the outlets hedge it throughout. Whether the case belongs in a database of attacks on cryptocurrency holders is a judgement call for you: the man held is an alleged scammer and the motive was recovering money lost in a fraud, not seizing a wallet. held_duration left null - 'un peu plus tard' is all the file says. arrests set to all because all three men described as involved were in pre-trial detention. The trial was set for 27 February 2026, which has now passed, so the status needs refreshing. Both articles also carry a paragraph about a separate Haute-Savoie abduction with a crypto ransom revealed 24 hours earlier; I used nothing from it. The AI summary's claim that the justice system is handling dual cases (kidnapping charges and a fraud investigation) appears in neither block.
## case 393
- **certainty** — record: Five people entered the home of a couple with three children. They held the entire family hostage for 40 minutes. | article (Ouest-France, actu.fr): Un homme aurait été séquestré avec toute sa famille le 8 janvier 2026 ... il s'agirait à nouveau d'une affaire sur fond de cryptomonnaie - Ouest-France keeps the whole account in the conditional, while actu.fr states it flatly
- flag `violence_torture` = null -> propose **unconfirmed**: 'On ignore si une personne a été blessée' - it is not known whether anyone was injured; the gendarmerie was seeking information about 'un cambriolage avec violences'
- flag `weapons` = null -> propose **unconfirmed**: no weapon is mentioned; neither article describes the entry or how the family was held
- flag `theft` = null -> propose **unconfirmed**: 'L'objectif des agresseurs : soutirer un code pour avoir accès à de la cryptomonnaie' - neither article says whether the code was obtained or anything taken
- label gaps: 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; a family with three children held together to extract one access code has no label distinguishing it from a single-victim invasion
- note: Thinnest file in the batch. Actu.fr's block is a second-hand relay of Ouest-France (986 chars, 6 paragraphs kept of 27) and the Ouest-France block is an archived paywall lead of 711 chars whose remaining lines are about two other incidents - a kidnapping at Saint-Léger-sous-Cholet on 9 January and a couple with two children assaulted the same day - which I did not use. Three flags left unconfirmed because the report says in so many words that it is not known whether anyone was hurt, and says nothing at all about weapons or whether the code was given up; outcome and arrests are null for the same reason, although a gendarmerie neighbourhood canvass a week later suggests nobody was in custody then. The file's AI summary claims PNACO took the case as one of three and names parallel investigations in Charente-Maritime and Maine-et-Loire; neither block on file says that. Small housekeeping point: the quarter field on this record reads 'Q1-2026' where the rest of the export uses '2026-Q1'.