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
Reports are associated with Hachinohe report involving the Nagata Mina persona. Saved descriptions and direct identifying details support a story hypothesis; they do not establish one verified incident or reconcile every reported total.
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: Both reports identify the Aomori man in his forties, the same 4.228-million-yen loss and the Nagata Mina persona. Direct source-supported identity, not independent verification.
Police describe a 4.228-million-yen romance scam, marriage promises and fictitious online-shop purchasing for profit. Five payments are reported; duplicate coverage of a case is not another case.
Membership evidence and limits
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: 0381e9b5b626358afae3bbaf4fe31365ba5271ccbb3088407a77d0534071d1d3
Why it is grouped here: Both reports identify the Aomori man in his forties, the same 4.228-million-yen loss and the Nagata Mina persona. Direct source-supported identity, not independent verification.
Police report a man in his forties in Aomori losing about 4.228 million yen; the headline explicitly identifies romance fraud and description names a dating app and LINE.
Membership evidence and limits
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: 03e1492ee37c1d32b0fafdd6c5ea1a0a2a6cef88d71e05bcabd6c3dffeef9ed4