# Jina — Ambiguity handling: no completed queries, confirmed by raw-file audit

Ambiguity/entity-collision block = Q23–Q29 (7 queries: Apollo, linkup.so, parallel.ai, Sonar, Mercury,
etc.). Checked every raw response file directly for `http_status`:

| query_id | file | http_status |
|---|---|---|
| Q23 | `jina/input-1/outputs/raw/search/Q23.json` | 402 |
| Q24 | `jina/input-1/outputs/raw/search/Q24.json` | 402 |
| Q25 | `jina/input-1/outputs/raw/search/Q25.json` | 402 |
| Q26 | `jina/input-1/outputs/raw/search/Q26.json` | 402 |
| Q27 | `jina/input-1/outputs/raw/search/Q27.json` | 402 |
| Q28 | `jina/input-1/outputs/raw/search/Q28.json` | 402 |
| Q29 | `jina/input-1/outputs/raw/search/Q29.json` | 402 |

**All seven ambiguity queries returned HTTP 402 (Payment Required) — zero completed.** This is
consistent with the already-documented Jina quota wall: Jina completed only Q01–Q10 (current-fact) and
Q42–Q47 (freshness), the two blocks that happen to sit before/outside the point where the free-tier
allowance ran out; every other block, including ambiguity, has zero successful calls.

**Disposition: Not scorable, permanently for this round.** There is no completed ambiguity-handling
data for Jina to grade — not a thin sample, an empty one. State this plainly rather than leaving the
criterion blank.