These reports are grouped for research, not as proof of one verified event. A timeline follows when URLs were observed in GDELT, not when the underlying events happened. Earlier observations do not prove the reviewed wording existed then.
2 source URLs2 source hosts
Retain these actually examined near-title variants as one bounded reporting-work hypothesis only. Each own text, legal phase, amount, date, country and harm limit stays source-specific; membership is not a unique case/person, independent corroboration, broader network or verified source-truth conclusion.
Source hosts may belong to the same publisher or repeat syndicated material. Review scope and methods.
Coverage timeline
Ordered by first observation in the collected metadata. Open a record for its assessed themes, original-source link and direct connections.
Why it is grouped here: Retain these actually examined near-title variants as one bounded reporting-work hypothesis only. Each own text, legal phase, amount, date, country and harm limit stays source-specific; membership is not a unique case/person, independent corroboration, broader network or verified source-truth conclusion.
Own construction-worker man60s/Hamada locality and female app contact do not describe fabricated affection or professional persona; relationship hold. App venue not actual messaging function, technology hold. Police announcement alone not investigation/arrest. No country/year from locale/date, job harm, clinical diagnosis or further sentence details.
Reported developments
These attributed statements apply to their specified subjects and scope. They do not establish guilt, a whole-article denial, or an unstated outcome.
development assertions
role
reported_development
basis
explicit
field
development
scope
single_case
value
reported_loss
reason
Keep reported_loss/single_case for the2.88mJPY cash-loss allegation under an investment pretext; cash wording supplies no crypto route.
Contextual association with this story hypothesis. It does not assert that every other member is directly linked to this report. Direct pairwise links are shown separately on each record.
Reviewed record revision: 0d4770a0d340ed946dc7f057f03346ac24770c7a117c6dde29398684082cf025
Why it is grouped here: Retain these actually examined near-title variants as one bounded reporting-work hypothesis only. Each own text, legal phase, amount, date, country and harm limit stays source-specific; membership is not a unique case/person, independent corroboration, broader network or verified source-truth conclusion.
Full SaninChuo own URL read independently; not receipt-based reuse of34. App venue gives no functional digital method; fabricated intimacy remains insufficient. No police investigation from announcement alone, country/year/crypto, employment harm from construction occupation, actual help use or compensation.
Reported developments
These attributed statements apply to their specified subjects and scope. They do not establish guilt, a whole-article denial, or an unstated outcome.
development assertions
role
reported_development
basis
explicit
field
development
scope
single_case
value
reported_loss
reason
Keep reported_loss/single_case for this own2.88mJPY cash allegation; repeated URLs do not add losses or corroboration.
Contextual association with this story hypothesis. It does not assert that every other member is directly linked to this report. Direct pairwise links are shown separately on each record.
Reviewed record revision: 8dee74b7c7480933f7c591cb5d7ee8172faf6f73298b34e4876abc86ac0c815d