Skip to content

F-2373Detected Oct 8, 08:51 UTC

Can I use my Unlimited hotspot allowance abroad?

Found in v3.4 · synthetic-hard-negatives v1.3 on synthetic-hard-negatives · Roaming & travel

Retrieval mismatchMediumOpenClaude Sonnet 5.5
Open gt_1064

Model answer vs gold answer

14% of model-answer words appear in the gold answer

Model answer

support-assistant v3.4

Yes, Unsupported: your full 50 GB hotspot allowance also applies while roaming in Zone 1.

Gold answer

Human-verified · synthetic-hard-negatives

Hotspot use abroad counts toward your Zone 1 roaming allowance (25 GB on Unlimited, 35 GB on Unlimited Plus), not the domestic hotspot allowance.

  • claimFlagged by the judge as unsupported or contradicted

Retrieved context

bge-m3 · hybrid (BM25 + dense, RRF) · top 3 passed to the generator

1 of 3 retrieved chunks are relevant · gold passage at rank 3

  1. 1

    Unlimited plan fair-use policy

    Hotspot allowance · kb-plans-019 · v2026.09

    Not relevant
    Domestic hotspot allowance is 50 GB.
    Similarity0.84
  2. 2

    Personal hotspot not working

    Hotspot limits · kb-device-140 · v2026.09

    Not relevant
    Hotspot use counts toward your plan's data.
    Similarity0.78
  3. 3

    Roaming fair-use

    Fair-use allowance · kb-roaming-011 · v2026.09

    Relevant
    All roaming data, including hotspot, counts toward the Zone 1 allowance.
    Similarity0.75

Judge verdict

LLM judge · Claude Opus 5.5 · rubric v3

0.16

rubric score · pass threshold 0.70

Domestic hotspot chunk outranks the roaming rule; the answer applies the wrong scope.

Diagnosis

Retrieval mismatch · Fair-use scope confusion

Root cause

Scope (domestic vs roaming) not represented in retrieval.

Suggested fix

Tag fair-use content by scope (same as F-2399).

Playbook: retrieval mismatch

The retriever returned the wrong article, the wrong section or a stale version.

Detection signals

  • High similarity on the wrong article title
  • Stale-version flag on top-ranked chunks
  • Exception clause split from its rule across chunk boundaries

Common fixes

  1. Filter or boost by effective date and locale metadata
  2. Re-chunk policy articles with heading-aware splitting
  3. Compare hybrid and dense retrieval on the mismatch subset
  4. Use parent-document retrieval so headings travel with chunks

Activity

1 event · 0 comments

  1. Relevant ·

    Detected by support-assistant v3.4 run and labeled retrieval mismatch