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-19.md
T
StellarCrowandClaude Fable 5.1 31056af77c feat(verify): batches 19 and 21 verified (5-1, 487-483; 472-463)
Writer agents from the dossiers; checker CLEAN on 19; on 21 one attribution
fixed (468) and a distance claim sourced from case 467's file removed from 466.
5 conflates two incidents; 3 fits no label; 468 fits no label (unexplained
death); 483 detention proposed 1 as a precedent call for Authority Misuse.

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

106 lines
26 KiB
Markdown

# Batch 19 — contradictions, flag proposals and notes for Sofia (2026-09-30)
## case 5
- **victim** — record: Dwayne Richards, a New York City firefighter | article (CNBC): the 27 May victim is only "The 28-year-old victim", unnamed and not called a firefighter; the firefighter appears separately — "The Observer article said that a New York City firefighter had been stabbed during a robbery of bitcoins that he had agreed to sell. But police on Friday told CNBC that that robbery, which occurred on Feb. 9, 'is not bitcoin related.'"
- **scenario** — record: Kidnapping | article (CNBC): "The 28-year-old victim told police he went to a street corner there to meet a man who had answered his Craigslist.com ad" and was robbed in a car; "the thugs then took the victim's cellphone, and drove off" — no abduction is described
- **violence / description** — record: Firefighter kidnapped, robbed of $1,100, & stabbed by crypto thieves; violence_torture 1 | article (CNBC): "The firefighter's credit card and PIN number were stolen, and he was stabbed in the arm, police said" — in the 9 February robbery police call not bitcoin related; no stabbing appears in the 27 May robbery
- **location** — record: New York, New York | article (CNBC): "The latest combination street-cyber crime occurred at around 11:30 a.m. on May 27 in the Crown Heights section of Brooklyn"
- **date** — record: May 27, 2015 | article (CNBC): 27 May is the date of the unnamed man's bitcoin robbery; the firefighter robbery in the record's description is dated Feb. 9, so the record's date and its description come from different incidents
- flag `violence_torture` = 1 -> propose **0**: no violence is described in the 27 May robbery; the stabbing belongs to the Feb. 9 firefighter case, which police say "is not bitcoin related"
- OFF-CASE link: url (cnbc.com) matches this record on date, amount and coin but names no firefighter; the same article's firefighter passage describes a 9 February robbery police say "is not bitcoin related". If the record's victim is the firefighter, then the 27 May robbery the article reports is a different incident and this file contains no article about the record's victim.
- OFF-CASE link: the same article carries a passage on the Dean Katz robbery (case 4), which was not used here
- label gaps: 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; a trade the victim himself advertised (a Craigslist ad offering bitcoins for sale) has no field; control shifted from a street corner to the buyer's car, which a single label cannot show
- note: This record looks like a merge of the Observer headline ("NYC firefighter kidnapped, robbed and stabbed by crypto thieves") with CNBC's 27 May Brooklyn robbery: the date, the $1,100 and the coin match the unnamed 28-year-old, while the name, the firefighter occupation, the kidnapping and the stabbing come from the other incident — which police told CNBC was not bitcoin related. I would split it: keep a 27 May Brooklyn P2P robbery with an unnamed victim, and treat the 9 February firefighter stabbing as a separate record that police say is not crypto-related (candidate for removal from the statistics). The victim's name cannot be supported from this file at all — the only source here names nobody.
## case 4
- **date** — record: February, 2015 | article (Observer): the article gives no date for the robbery — only "One day, he received a call", the caller's wish "to gamble during the Super Bowl", and the piece's own byline of 02/20/15
- **location** — record: New York, New York | article (Observer): "someone ... who wanted to visit him out in Queens at a secure location"
- **money_wanted / coin_type** — record: $12,000, BTC | article (Observer): "forced him to transfer $8,500 worth of bitcoin. Then, the robber took $3,500 in cash" — the $12,000 is the combined total, not all of it crypto
- **detention flag** — record: kidnappings 0 | article (Observer): "he held Mr. Katz up at gunpoint and forced him to transfer $8,500 worth of bitcoin"
- flag `kidnappings` = 0 -> propose **1**: "When the person arrived, he held Mr. Katz up at gunpoint and forced him to transfer $8,500 worth of bitcoin" — the record's flag legend counts being held at gunpoint
- label gaps: 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; money_wanted cannot show that only $8,500 of the $12,000 was cryptocurrency and $3,500 was cash; a single robbery standing in for what the victim describes as a pattern among in-person traders has no field
- note: One source, and it is a round-up: the Observer piece leads on the firefighter stabbing (case 5) and only the Katz passage was used here. The article never dates the robbery, so February 2015 rests on the publication date. The venue is described only as "a secure location" in Queens that the caller came to — I recorded venue_of_control as the victim's workplace on that basis, since Katz's business is these meetings, but the article does not say what kind of place it was. Detention: proposed 1, held at gunpoint. money_wanted would be more accurate as $8,500 in BTC plus $3,500 cash.
## case 3
- **date** — record: January 22, 2015 | article (Bitcoinist): "The machines were stolen over the past four weeks"; the second article says "Late last month, two Bitcoin ATMs were stolen" and "About two weeks ago, at Warries Thai food the door was forced" — two thefts on different days, neither dated to 22 January
- **scenario** — record: Armed Robbery in Public Space | article (Bitcoinist): "the door was forced and [thieves] removed the BitAccess ATM"; "The burglars forced their way into the venue at 6:55 AM" — forced entry at closed premises, no weapon and no person confronted
- **victim** — record: Martin Wismeijer | article (Bitcoinist): "This ATM was not owned by Mr.Bitcoin but we know the owner of the restaurant" — one of the two machines was not his; the second article also spells him "Martijn Wismeijer"
- **crypto stolen** — record: description and notes say two Bitcoin ATMs were stolen (no coin or amount recorded) | article (Bitcoinist): "The ATMs are useless as they are remotely disabled and contain no Bitcoin or other crypto"; "the crypto itself was never at risk"
- label gaps: the eleven labels have no entry for a burglary of unattended commercial premises: no victim was present, no weapon appeared and nothing was extorted from anyone; the record carries two separate thefts, at two venues, weeks apart, as one case with one date; the loss fell on the venues and on individual traders whose fiat was inside the machines, which the single victim field cannot show
- note: Two thefts are carried on one record with one date; the file supports neither the date nor the "armed" in the scenario. I left the sequence empty because no glossary label covers a burglary of unattended premises — if the export needs a label, Armed Robbery in Public Space is the nearest but is wrong on the two points above. Note also that the bulk AI summary on this record claims "Approximately 2 BTC" stolen; Wismeijer says the opposite, the machines held no crypto and none was at risk. The loss was hardware (about 8,700 and 2,600 euros) plus traders' fiat inside the machines.
## case 2
- **date** — record: January 3, 2015 | article (CoinDesk report quoted in the sheet / Cointelegraph): the first report is datelined Nov 4, 2015 and puts the theft "at approximately 10:45 PM EDT on Tuesday night" that week; the second says "On November 3, two robbers stole a Lamassu Bitcoin ATM at the Village Smoke Shop"
- **theft flag** — record: theft 0 | article (CoinDesk report quoted in the sheet): "had its Lamassu bitcoin ATM stolen"; the machine held about US$2,000 and the unit is valued at US$7,000
- **attackers** — record: not stated in the record | article (CoinDesk report quoted in the sheet / Cointelegraph): the police report has suspects inside confronted by employees plus "two additional suspects ... waiting in the car", while the second article says "two robbers"
- **victim role** — record: victim Amanda McCollum | article (CoinDesk report quoted in the sheet / Cointelegraph): "store manager Amanda McCollum" in the first report; "Amanda McCollum, an employee in Midtown's Village Smoke Shop, witnessed the crime" in the second
- **reports** — record: reports CT | article (CoinDesk report quoted in the sheet): the first article block is a CoinDesk piece — "According to a report provided to CoinDesk by the Atlanta Police Department" — filed under the Cointelegraph URL on the record
- flag `theft` = 0 -> propose **1**: "the Village Smoke Shop on Juniper Street had its Lamassu bitcoin ATM stolen"; "the thieves got away with Bitcoin ATM (also called BTM) filled with about US$2,000" — the record's own notes say a Bitcoin ATM was stolen
- OFF-CASE link: both Cointelegraph blocks close with a passage on the two Amsterdam bitcoin ATM thefts (case 3), which was not used here
- label gaps: the target was a machine rather than a person or their keys, and no crypto was reachable; the label set assumes a human holder; the reconnaissance a week earlier — two men asking questions about the ATM, then a wallet stolen from the office — is a separate incident the record cannot carry; the victim field holds an employee's name while the loss fell on the shop and the machine's owner
- note: The date is the clearest problem: both articles put this robbery in early November 2015, not 3 January 2015. theft should be 1 — the record's own notes say the ATM was stolen while the flag says 0. Nothing crypto was taken: the loss was the machine (US$7,000) and about US$2,000 of cash inside, and Cointelegraph says only the owner could ever get bitcoins out of it, so money_wanted and coin_type are rightly empty. The first article is a CoinDesk report even though the record credits CT, and Amanda McCollum is the staff member who confronted the robbers rather than the party that lost anything.
## case 1
- **date** — record: December 29, 2014 | article (WIRED): 12.29.14 is the WIRED byline. The article places the swatting "just days after ... Elliot Rodger had killed six people near Santa Barbara's University of California campus", says the caller "called the Finney's home number nine times in the two months after the attack", and says "Hal Finney died in August" — so the attack preceded August 2014 and the record's date is the publication date
- **weapons** — record: weapons 1 | article (WIRED): no weapon is attributed to the caller; the armed presence is the SWAT response — "she found the building surrounded by police, and a helicopter buzzing in the air above"
- **money_wanted / coin_type** — record: both empty | article (WIRED): "an extortion fee of 1,000 bitcoin—worth more than $400,000 at the time"
- flag `weapons` = 1 -> propose **0**: no weapon is described in the article; the only armed presence is the police response the hoax was meant to provoke — WIRED describes swatting as intended "to provoke an armed police response to the victim's home"
- label gaps: 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; nothing records that the armed response was carried out by police acting in good faith on a false report; the victim's medical condition — what made a half hour on the lawn dangerous — has nowhere to go; the caller is reported to have extorted several other bitcoin holders, and the serial pattern cannot be linked across records
- note: Two things for the owner. First, the date: 29 December 2014 is WIRED's publication date, and the article's own timeline puts the swatting before Hal Finney's death in August 2014 — the record needs a corrected or partial date. Second, the weapons flag needs a rule for swatting: the only weapons in these cases belong to the police who answer the hoax, so if the flag records weapons brought by attackers, every swatting is 0; I proposed 0 on that reading. money_wanted and coin_type could carry 1,000 BTC / more than $400,000 at the time. One source only, and Fran Finney is the narrator for most of it.
## case 487
- **crypto stolen** — record: description says the stolen phone held the access codes to a cryptocurrency account worth approximately USD 25,000 | article (franceinfo / actu17 / Var Actu): the franceinfo and actu17 headlines say the account was stolen ("un compte de cryptomonnaies ... dérobé"), while Var Actu says no further detail has been disclosed about the fate of the digital assets; the body text of all three says only that a phone holding the access codes was taken
- **weapons** — record: weapons 1 | article (franceinfo / actu17 / Var Actu): no weapon appears in any of the three accounts; the only basis is the prosecutor's legal qualification "extorsion avec arme"
- **date** — record: September 6, 2026 | article (franceinfo / actu17 / Var Actu): all three give "dimanche 6 septembre" with no year; franceinfo says it learned of the attack on the Monday, and the pages were retrieved on 9 September 2026
- **money_wanted / coin_type** — record: both empty | article (franceinfo / actu17 / Var Actu): a crypto account "of a value of about 25,000 dollars"; no coin is named and no sum was demanded of the victims
- OFF-CASE link: all three pages close with round-up material about other cases — the PNACO count of 135 crypto kidnappings, the April 2026 Dompierre-sur-Mer couple (Charente-Maritime) and the 25 August Yvelines attack — none of which was used for this case
- OFF-CASE link: the franceinfo page's kept text also carries a long tail of unrelated news teasers, which was ignored
- label gaps: 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; two victims held in one attack are carried on one record with a single victim field; nothing records how the pair got free after the attackers fled
- note: Three French reports, but effectively one account: actu17 says it is confirming franceinfo's information and both it and Var Actu cite the same source close to the case. Two points for the record. The 25,000 dollars is the value of the account the codes opened, not a confirmed loss — no source says the account was emptied, so money_wanted/coin_type should carry that caveat if filled. And the weapons flag rests only on the prosecutor's charge wording; no witness account of a weapon exists in this file. The record's own description says "tied up", which the sources support.
## case 486
- **detention flag** — record: kidnappings 0 | article (VE Media): "the victim got into the suspects car that was parked at a building at 5801 Biscayne Blvd", was held under a handgun and repeatedly threatened with death, and "then escaped and called an Uber"
- **date** — record: December 8, 2025 | article (VE Media): "the two kept in contact and met up in South Florida on the 8th of December" — the kept text gives no year, dating the arrest only to "Tuesday" and bond court to "Wednesday" and calling the robbery "an early-December armed robbery"
- **money_wanted / coin_type** — record: both empty | article (VE Media): "$562,155 worth of crypto" transferred plus jewellery totalling "approximately $413,500"; no coin is named
- flag `kidnappings` = 0 -> propose **1**: "the victim got into the suspects car", where Johnson "brandished a small black handgun" and "continuously told him that he would kill him if he didn't comply"; the victim "then escaped and called an Uber" — held at gunpoint to execute the theft
- label gaps: a two-month acquaintance formed at a nightclub and then used as the approach cannot be distinguished from a cold ambush; the report does not say the December meeting was arranged as a trap; the record cannot hold the split between the crypto ($562,155) and the jewellery (about $413,500); a victim who escaped from a robbery that had already succeeded has no outcome that fits cleanly
- note: One source, a UK aggregator page that quotes the Miami Police Department report at length; the alias Buckfiddy appears only in its headline and the body's "the UK Rapper" is unexplained. The kept text carries no year, so 2025 is not verifiable from this file — worth a second source. Detention: proposed 1 (held at gunpoint in the car, escaped afterwards). arrests recorded as "all" because the report describes a single perpetrator and he was arrested and held; money_wanted could carry $562,155 in crypto with the $413,500 of jewellery noted separately.
## case 485
- **location** — record: Czeladz, near Katowice, Silesia | article (cryptobriefing / u.today / KuCoin): "Suszek's last confirmed location was a fuel base in Czeladzi, Poland" (cryptobriefing), "a fuel depot in Czeladz" (u.today), a fuel station in Czeladź (KuCoin); none of them places it near Katowice or in Silesia — u.today gives Katowice only as his birthplace
- **description** — record: His sister subsequently received voice and text messages in which Suszek begged for Bitcoin to secure his release | article (u.today / crypto.news): u.today's sentence reads "Suszek's sister started sending harrowing voice and text messages, in which he begged for Bitcoin to secure his release" — the page is garbled on who sent them; crypto.news attributes the messages to the family receiving them, citing the NYT, and says they establish nothing about what happened to him
- **attackers** — record: Marian W. (Marian Wszolek) | article (cryptobriefing / crypto.news / u.today): cryptobriefing and the KuCoin flash give only "Marian W."; crypto.news and u.today name "Marian Wszolek", and u.today says he has since vanished
- **money_wanted / coin_type** — record: both empty | article (crypto.news / u.today): the messages asked for Bitcoin with no figure reported anywhere; the 4,500 BTC discussed (about $330 million per u.today) is described as exchange-linked and under Suszek's control, not as the ransom demand
- flag `violence_torture` = null -> propose **threat only**: the only violence in the file is a reported threat — his captors "were threatening to cut off his fingers over a debt" — and no injury is evidenced; the ax through his Ferrari windshield belongs to an earlier, separate incident
- flag `drugs_alcohol` = null -> propose **0**: nothing on drugs or alcohol in any of the four sources
- flag `weapons` = null -> propose **0**: no weapon appears in the disappearance; the ax used on his Ferrari windshield is a separate earlier incident
- flag `life_taken` = null -> propose **unconfirmed**: "No body has been recovered. No confirmed sighting has surfaced"; crypto.news says "no publicly cited court judgment has established that he is dead"
- OFF-CASE link: the crypto.news and u.today pages are largely about the Zondacrypto collapse, the missing successor Przemysław Kral, on-chain hot-wallet analysis and Polish MiCA legislation; only the passages on Suszek's disappearance were used
- label gaps: an unresolved disappearance that is only reported as a kidnapping has no label for an unestablished attack; nothing in the file confirms he was taken, only that his family received messages saying so; the file cannot say whether the business meeting at the fuel depot was the lure; 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; there is no outcome value for a victim who was never found and has not been declared dead
- note: Four links but fewer sources than it looks: the KuCoin flash is a Spanish-language rendering of the same text as the cryptobriefing piece, near sentence for sentence, so treat them as one. The load-bearing reporting is a New York Times investigation none of these pages reproduces; it should be fetched before this case is called verified, because everything about the kidnapping itself reaches us at second hand through the family's messages. arrests left null: the only person charged has himself disappeared, so no one is described as in custody. outcome left null because the value list has nothing for a victim never found and not declared dead. u.today's closing line that the whole operation "is believed to be a long-running scam" is commentary about the exchange, not evidence about the disappearance, and was not used.
## case 484
- **arrests** — record: not recorded | article (spilled.gg / tradersunion.com): spilled.gg: "There has been no public confirmation about arrests, charges, or whether the attackers have been identified" against tradersunion on Lopp: "authorities have arrested two suspects so far"
- **date** — record: January 13, 2026 | article (spilled.gg): no source on file dates the attack; the only timing is that he was "back online after roughly five months of silence", on pages retrieved 9 September 2026
- **attackers** — record: no number recorded | article (trendsmask.com): "Three armed individuals invaded his home in Sweden" on trendsmask, an aggregator that says its details come from forum summaries and reposts and "may be secondhand"; spilled.gg gives no number
- **detention duration** — record: not recorded | article (trendsmask.com / tradersunion.com): "He was allegedly held hostage for about four hours" (trendsmask) against "intruders tortured him for hours" (tradersunion, reporting Lopp); spilled.gg gives no duration at all
- **theft** — record: theft 1, no amount | article (spilled.gg): no cryptocurrency was obtained — "demanded cryptocurrency he didn't have", "He wasn't, at least not in any form they could grab"; what left the house was Pokémon cards, car keys and ID
- flag `weapons` = null -> propose **1**: all three accounts call them armed — "armed intruders broke into his family home", "Three armed individuals", "armed robbers" — but no source names the weapon
- OFF-CASE link: url_2 (x.com/lopp) was not transcribed and url_4 (bo3.gg) yielded almost nothing; neither was used
- OFF-CASE link: the kept spilled.gg text carries one unrelated teaser headline about an 81-year-old Minecraft streamer being swatted, which was not used
- OFF-CASE link: the tradersunion page's kept text closes with unrelated Lopp items on Bitcoin Knots and the Bitcoin Research Kit, which were not used
- label gaps: the target was chosen for holdings he did not have, and no field records an attack built on a wrong guess; the sequence cannot show that the violence and the gasoline continued after it was clear there was no crypto to take; a crime that reaches the record months later through the victim's own stream, with no official confirmation of anything, has no evidence-quality field
- note: Source quality is the issue here, not the facts of the attack. The one solid account is the victim's own return stream as reported by spilled.gg. Trendsmask.com is an aggregator summarising Reddit and search results and says so; it is the only source for three attackers and for the four-hour detention. Tradersunion reports a Jameson Lopp post it says was deleted, and describes Lopp as a "board member at L'Oréal", which nothing else on file supports — I would not lean on that page for anything but the fact that Lopp claimed two arrests. So held_duration "hours" rests on secondhand text, and arrests is left null because the two sources flatly disagree. Nothing on file dates the attack, so 13 January 2026 needs a source, ideally the Swedish coverage the viewer mentions. weapons: proposed 1 on "armed intruders", type unknown. No amount was ever demanded — only access — so money_wanted should stay empty.
## case 483
- **date** — record: March ?, 2022 | article (Analytics Insight): the report places the thefts only "in 2022" — "The probe looked into the events involving police interference in Ufa in 2022" — and gives no month
- **money_wanted / coin_type** — record: both empty | article (Analytics Insight): "at today's rate, the Bitcoins transferred illegally back then were worth around 20 million rubles. The figure equaled $700,000." — a present-day valuation of coins moved in 2022
- **detention flag** — record: kidnappings 0 | article (Analytics Insight): the victims are described throughout as detainees in the officer's custody, and the court found he used physical violence against them
- flag `kidnappings` = 0 -> propose **1**: the victims were "persons under arrest during the legal process" whose phones he seized during those detentions, and the court found he used physical violence against them — the custody was the officer's own and the instrument of the theft (DEFINITIONS ruling 2)
- flag `weapons` = null -> propose **0**: no weapon appears anywhere in the report
- OFF-CASE link: the fetched page pads the report with unrelated Bitcoin market commentary (price, market cap, circulating supply), none of which was used
- OFF-CASE link: url_2 (x.com/wublockchain12) was recorded as a social post and not transcribed; url_3 (tass.ru) yielded almost nothing, so neither could be read
- label gaps: detention that was lawful in itself, and then became the instrument of the theft, cannot be distinguished from detention by criminals; the record cannot say how many victims there were, and the victim field carries only "Multiple detainees"; a theft spread over repeated routine stops has no single date, which the date field forces
- note: The detention flag is a ruling call and I have proposed 1: the holding was lawful police custody, but it was this officer's own custody and it was how the theft was carried out, which is what ruling 2 covers. If the owner prefers the flag to mean detention by criminals only, this case goes back to 0 and Authority Misuse cases will need their own note. Beyond that, one usable source only, and a weak one: a low-grade aggregator page whose prose is garbled in places ("The officials who remained unnamed were engaged in handling persons under arrest") and which pads the story with Bitcoin price commentary. The TASS link returned almost nothing and the X post was not transcribed, so the officer's name, the number of victims and the month of the thefts cannot be verified from this file. money_wanted and coin_type could carry about 20 million rubles / $700,000 and BTC, with the caveat that the figure is a valuation at the date of the report.