Included for relevance; source claims are not independently verified. This record is based on saved titles and descriptions unless a separate deeper-reading assessment is explicitly shown. Observation dates are not incident dates. An arrest or charge is not a conviction.
How to read this record
Kunisakifemale40s reported780000JPYcashloss inSNSRomancefraud; own travelpretext wants tovisitJapan butcostsmoney. No paymentdates or explicitactualforeignorigin.
Evidence basis: saved title description
Places in the available evidence
No geographic role could be established from the available text.
Unlisted locations remain unknown. Nationality, language and web address alone do not establish where a scam happened.
Current source qualifications
These attributed statements apply to their specified subjects and scope. They do not establish guilt, a whole-article denial, or an unstated outcome.
source specific current qualifications
text
Kunisakifemale40s reported780000JPYcashloss inSNSRomancefraud; own travelpretext wants tovisitJapan butcostsmoney. No paymentdates or explicitactualforeignorigin.
No selected approved assertion for that role; not a categorical source denial
unknown role reasons
date.incident
No selected explicit event-calendar literal; relative dates, publication/URL years and durations cannot fill this role.
country.victim
Kunisaki place unvalidated; claimed Japan visit is a persona/pretext, not a core country.
date.procedural
No selected explicit event-calendar literal; relative dates, publication/URL years and durations cannot fill this role.
country.operation
Kunisaki place unvalidated; claimed Japan visit is a persona/pretext, not a core country.
country.publisher
Publisher location is not selected as a core-case country.
country.jurisdiction
Kunisaki place unvalidated; claimed Japan visit is a persona/pretext, not a core country.
source truth verified
false
case identity verified
false
currentcoding34 SQL approved
false
ownrole assertion scope limits
Item 1
role
reported_development
field
development
scope
single_case
value
reported_loss
exact reason
Own cash loss claim; planned visit/persona and police announcement do not approve a country or event-year.
assertion index
0
final QC role code join not bypassed
true
exact ROOT qualified ownrole record note
PROPOSED role interpretations from saved admitted notes, not final country/calendar/development approval. Unknown is a proposal partition, not categorical source absence. All original actors/places/calendars/developments/amounts/limits remain exact in the separate three-layer history. No new SOURCE reading or independent truth validation.
all stronger current overlaps and21plus3U preservation still required
true
is entire code dimension denial
false
exact ROOT qualified record note
Kunisakifemale40s reported780000JPYcashloss inSNSRomancefraud; own travelpretext wants tovisitJapan butcostsmoney. No paymentdates or explicitactualforeignorigin.
Source statement flags
raw verified
false
is publisher quote
false
source truth verified
false
interpretation not source literal
true
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
Own cash loss claim; planned visit/persona and police announcement do not approve a country or event-year.
These labels describe the available reporting. “Not reported” does not mean a harm did not happen. A theme's stage applies to that statement, not every claim in the article.
Only direct reviewed connections are shown. Shared wording is weaker evidence than a supported case connection. A connection through a third article does not establish that two reports concern the same case.
No direct connection is recorded. This does not establish that the story is unique.
A page can change after it first appears. Observation dates record when its URL was seen; they do not prove that the wording assessed here was present on every date.
Record: eae3563de41a9d949d7492dca5f93856357f81e68f1fb1defeaebee9af0cf893 Decision: fa1b8a8829efb56bd362d7dfa4a08df46f7d0f3798d25fd58fab2625409660a7 Base reviewed revision: 84ff9770c35b23050fedd4ef54dd8043bd00852c2d10b9bc61c7bed2a7f0a5b6
The local research archive retains source hashes, quoted evidence and review records. This collection does not redistribute full publisher articles.