AI monitoring UK public information · England · Scotland · Wales · Northern Ireland
PRESTON|07:12|England|Transport

Signalling failure suspends services between Preston and Carlisle

Infrastructure data and operator notices corroborate; cause statements remain attributed, not established.

CORROBORATEDProof Score 81Independent lineages 5Primary sources 2Last AI recheck 6 minutes ago

What we know

  • Services between Preston and Carlisle are suspended.
  • The infrastructure operator has published a disruption notice citing a signalling fault.

What we don't know

  • ?When services will resume; estimates differ between operator notices.
  • ?The underlying cause of the fault.

Summary

Generated only from the evidence dossier

Detected via operator disruption feeds rather than social signal; social discussion followed 9 minutes later.

Rail infrastructure data is treated as highly authoritative for this specific claim class.

CLAIM-014

Assertion type: FACT

Rail services between Preston and Carlisle are suspended.

CORROBORATED
81
Claim ID
CLAIM-014
Proof Score
81
Proofed at
Last rechecked
6 minutes ago
Evidence count
2
Independent lineages
5

Principal score factors

  • Infrastructure operator disruption feed+34
  • Two train operators' independent notices+26
  • Live departure boards show cancellations+21
  • Resumption time conflicts between notices-10

Evidence

  • DATAEV-21 · lineage L1 · 07:02
    Infrastructure disruption feed

    Signalling fault logged 06:58; line blocked northbound and southbound.

    Authoritative for: Network status

  • OFFICIALEV-22 · lineage L2 · 07:10
    Train operator notice

    Do not travel advice issued for the affected section.

    Authoritative for: Operator advice

Source tree · information lineage

  1. OriginInfrastructure feed

    Machine-published, primary

  2. Hop 1Operator notices

    Independent republication with own data

  3. Hop 2Passenger posts

    Corroborative but downstream

The Sceptic · adversarial verification

  • Checked for a stale feed entry: timestamps refreshed twice during review.
  • Awaiting a second primary source before the claim can move to PROOFED.

Evidence graph

How the conclusion was constructed

  1. 01EVENT
  2. 02CLAIMS
  3. 03ORIGINAL SOURCES
  4. 04INDEPENDENT LINEAGES
  5. 05PRIMARY EVIDENCE
  6. 06OFFICIAL STATEMENTS
  7. 07DATA
  8. 08MEDIA
  9. 09SECONDARY REPORTING
  10. 10CONTRADICTORY EVIDENCE

Contradictions

Recorded, never hidden

  • One operator notice gave a 10:00 resumption estimate; a second gave 12:00. Both are recorded as ESTIMATE, not FACT.

Proof ledger

Permanent chronological record

  1. 07:02
    SIGNAL DETECTED — infrastructure disruption feed
  2. 07:04
    CLAIM-014 created
  3. 07:12
    CLAIM-014 → CORROBORATED · Proof Score 81

Corrections

Built in, not a footnote

No corrections issued for this story.

Other investigations