rag-contract question answering over a fixed corpus, with a measured contract

← the fixed question set

How is a percent-encoded octet written in a URI?

q02 · grounded · HTTP 200 · index 0fc1763d6701

What survived the check — each claim with the passage that supports it

A percent-encoded octet is written as a character triplet consisting of the percent character "%" followed by the two hexadecimal digits representing that octet's numeric value.
rfc3986#2.1 — 93% of this claim's content words appear in that passage.

What was retrieved — the passages the drafter saw, and nothing else

ranksectionscore
1 RFC 3986 Section 2.1: Percent-Encoding 0.7876
2 RFC 3986 Section 2.4: When to Encode or Decode 0.7134
3 RFC 3986 Section 6.2.2.2: Percent-Encoding Normalization 0.7012
4 RFC 3986 Section 1.2.1: Transcription 0.6651
5 RFC 3986 Section 2.5: Identifying Data 0.6322
8 RFC 3986 Section 7.3: Back-End Transcoding 0.6189
10 RFC 3986 Section 2: Characters 0.5987

What this request spent — against the deadline it was held to

0.833 ms of a 150.0 ms deadline: retrieval 0.467 ms, drafting 0.005 ms, grounding 0.201 ms. A request that spends the whole of it is abandoned rather than answered — a grounding check stopped part way through has not checked the remaining claims.

The same answer as JSON: /answer/q02.