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/labels/not-applied.json
T
StellarCrow 41766c68a2 chore: final state before the move to gart/gart-databases
Commits the work done since 2026-10-01 that was still local: the four-step
label and flag passes, the triage and recheck files, the v1 exports of
2026-10-06 and 2026-10-07, the split dossiers, and the Lopp PR 234 batch
(scripts, agent prompts, reader and checker files, the flag re-read of
2026-10-17, the review workbook and the import set of the 57 cases added
to stats2 as 506 to 562). Raw HTML and node_modules stay out (.gitignore).

The stats2 material in use was copied to gart/gart-databases (stats2/) on
2026-10-17; README-START-HERE.md now says so. This repo is closed.
2026-10-17 10:47:37 +02:00

192 lines
10 KiB
JSON

[
{
"id": 41,
"kind": "label check: change turned down by two of three readers",
"field": "targeting",
"proposed": [
"unknown"
],
"quote": "the gang lured the two brothers, claiming that they could sell them Bitcoin",
"detail": "no stated reason for choosing the brothers; label other has no stated reason behind it | third reader: keep the current value. The text states how the gang reached the brothers (they were looking for a bitcoin seller and the gang offered to sell), so a stated reason exists and unknown does not clearly pass better."
},
{
"id": 53,
"kind": "label check: change turned down by two of three readers",
"field": "who_was_attacked",
"proposed": [
"holder",
"relative or partner"
],
"quote": "The gang demanded 10 lakh rupees ($15,000) from his family members",
"detail": "attackers contacted Shah's family with a ransom demand; relatives contacted by the attackers count | third reader: keep the current value. Owner's rule: family members who were not present were not attacked, and the text also says the families were unaware of the abduction."
},
{
"id": 53,
"kind": "label check: change turned down by two of three readers",
"field": "targeting",
"proposed": [
"unknown"
],
"quote": "had been lured into the region by gang members who claimed to be selling bitcoins at a low price",
"detail": "label other needs a stated reason that fits none of the list; the text gives how he was lured, not why he was chosen | third reader: keep the current value. The text gives a stated route to the victims (traders drawn by a cheap bitcoin offer), so unknown does not clearly pass better than other."
},
{
"id": 114,
"kind": "label check: change turned down by two of three readers",
"field": "outcome",
"proposed": "fought off",
"quote": "Je pousse la personne, je hurle, j'ai mis un ou deux coups",
"detail": "the attacker was never described as fleeing; Simonin hit him and then went inside and locked the door, so fought off does not fit | third reader: keep the current value. The text never says the attacker gave up and fled; the victim hit him and then withdrew behind a locked door."
},
{
"id": 144,
"kind": "label check: change turned down by two of three readers",
"field": "attack",
"proposed": [
"Kidnapping",
"Armed Robbery"
],
"quote": "an armed robbery took place 2 days ago, kidnapping my partners",
"detail": "only the partner's Telegram post says kidnapping/abduction; the text does not show them taken away or held at a place the attackers control, so the Kidnapping test is not met | third reader: keep the current value. Only a partner's Telegram post uses the word kidnapping; no text shows the two being taken away or held at a place the attackers controlled."
},
{
"id": 209,
"kind": "label check: change turned down by two of three readers",
"field": "targeting_accuracy",
"proposed": [
"correct"
],
"quote": "400 ETH (1.2 million euros) to calm the kidnappers",
"detail": "crypto was transferred to the attackers, which passes the test for correct; 211 with the same fact is already correct | third reader: keep the current value. The crypto was sent by company executives and investigators, which does not show the victim held assets roughly as sought."
},
{
"id": 236,
"kind": "label check: change turned down by two of three readers",
"field": "targeting_accuracy",
"proposed": [
"correct"
],
"quote": "A ransom of $43,000 in digital currency was paid",
"detail": "crypto was transferred to the captors of a couple running a crypto business | third reader: keep the current value. The ransom was paid by a friend, which shows nothing about the couple's own holdings."
},
{
"id": 240,
"kind": "label check: change turned down by two of three readers",
"field": "targeting",
"proposed": [
"business counterparty"
],
"quote": "a friend introduced him to Benjamin, who told him to bring the cash to MS Palya Circle",
"detail": "'other' has no stated reason; the attackers' middleman set up a currency trade with him, which fits business counterparty | third reader: keep the current value. The attackers met him only through the arranged trade itself; no prior trade, investment or dispute is described."
},
{
"id": 263,
"kind": "label check: change turned down by two of three readers",
"field": "who_was_attacked",
"proposed": [
"holder",
"relative or partner"
],
"quote": "family was instructed to change drop-off locations multiple times",
"detail": "the family was only reached through forced calls made by the victim; the summary shows no attacker confronting or contacting them directly, and the owner's rule says an absent family member was not attacked | third reader: keep the current value. Owner's rule: the family was not present and was reached only through forced calls, so it was not attacked."
},
{
"id": 402,
"kind": "label check: change turned down by two of three readers",
"field": "targeting_accuracy",
"proposed": [
"wealth overestimated"
],
"quote": "the male victim said he did not have bitcoin",
"detail": "attackers sought $66 million in crypto; the victim held none | third reader: keep the current value. The only support is the victim's own denial to his attackers, and one source says the victims had none or refused access, so his holdings are not shown."
},
{
"id": 408,
"kind": "label check: change turned down by two of three readers",
"field": "approach",
"proposed": [
"Social Engineering: social invitation",
"seized in the street or a public place"
],
"quote": "a vehicle with four people inside blocked his path in front of the restaurant and the suspects forced him into it",
"detail": "the seizure followed a planned lure by the woman; seized in a public place requires no deception, and the current social invitation label already covers how he was brought there | third reader: keep the current value. The seizure outside the restaurant followed a planned lure, and the public-place label requires no deception."
},
{
"id": 424,
"kind": "label check: change turned down by two of three readers",
"field": "outcome",
"proposed": "rescued",
"quote": "Both fled after hearing a helicopter circling above.",
"detail": "the text does not say the helicopter was police or that anyone arrived; the attackers left of their own accord, leaving the victim bound, which fits released | third reader: keep the current value. The text does not say whose helicopter it was or that anyone reached the house before the two men left."
},
{
"id": 451,
"kind": "label check: change turned down by two of three readers",
"field": "targeting",
"proposed": [
"public profile"
],
"quote": "her son a young influencer very well known on social media and a YouTuber",
"detail": "the family was known through the influencer son, consistent with the public profile label given to case 448 | third reader: keep the current value. The son is described as a well-known influencer, but no text shows he was known as a crypto holder or how the attackers chose the family."
},
{
"id": 454,
"kind": "label check: change turned down by two of three readers",
"field": "targeting_accuracy",
"proposed": [
"correct"
],
"quote": "Three transfers totalling 14,000 euros in cryptocurrency",
"detail": "crypto was transferred from the victim, so the targeting hit a holder | third reader: keep the current value. The 14,000 euros came after he was forced to ask his partner and a friend for funds, so the transfers do not show his own holdings."
},
{
"id": 457,
"kind": "label check: change turned down by two of three readers",
"field": "approach",
"proposed": [
"unknown"
],
"quote": "violent banging on the door of their house",
"detail": "the intruders never got inside and no break-in is shown, so forced entry is not supported | third reader: keep the current value. The text does describe how the intruders came at the house (violent banging on the door at night), so unknown does not clearly pass better."
},
{
"id": 472,
"kind": "label check: change turned down by two of three readers",
"field": "approach",
"proposed": [
"unknown"
],
"quote": "put the men to flight before they got inside",
"detail": "they never entered and no forcing is described; a crowbar in the bag does not show forced entry | third reader: keep the current value. The text does say how they meant to get in (a crowbar and a man tasked with opening the door), so unknown does not clearly pass better."
},
{
"id": 473,
"kind": "label check: change turned down by two of three readers",
"field": "approach",
"proposed": [
"unknown"
],
"quote": "took flight without managing to get inside the dwelling",
"detail": "no force or break-in is described, only an attempt | third reader: keep the current value. The text describes four men with crowbars attempting to break into the home, so unknown does not clearly pass better."
},
{
"id": 493,
"kind": "label check: change turned down by two of three readers",
"field": "approach",
"proposed": [
"unknown"
],
"quote": "the three climbed the fence of the property. The garden's perimeter detection system went off immediately and put them to flight before they could get inside the house",
"detail": "forced entry requires breaking or pushing into the home; they never got in | third reader: keep the current value. The text says the three climbed the property fence before the alarm drove them off, so the way they came is described and unknown does not clearly pass better."
},
{
"id": 497,
"kind": "label check: change turned down by two of three readers",
"field": "targeting_accuracy",
"proposed": [
"unknown"
],
"quote": "No crypto demanded. They asked for cash; with none on site, they took wallets and other valuables from the people inside.",
"detail": "the text does not show the shop held far less than the attackers believed; they demanded cash, not crypto | third reader: keep the current value. The robbers demanded cash and the shop had none on site, which fits wealth overestimated at least as well as unknown."
}
]