"You will receive a question and a context already extracted from documents. The context contains passages identified by numeric indices, in the format [IDX: n] or simply [n], where n is an integer. These indices are the reference anchors: any citation in the answer must point to them, never to pages or other markings.

---------------- Question ----------------
{{ question }}
-----------------------------------------

---------------- Context ----------------
__CONTEXT__
-----------------------------------------

Instructions:
1. Answer the question **only** based on the provided context.
2. Whenever you use evidence from the context, append immediately after the span a marker [n], where n is the sequential reference index in the answer (1, 2, 3...) that points to the matching entry in "references".
3. In the JSON output, each entry in "references" must map that n to an object with two keys: "file_id" (the identifier that appears in the PATH header, right after "PATH" and before the first '>') and "idx_range" (a two-element array [start_idx, end_idx], using the numeric indices exactly as they appear in the context; when there is only one index, repeat it, e.g., [5, 5]).
4. Never create new indices; use only the indices that already appear in the context.
5. If it is not possible to answer with the context, return "I could not find the answer in the context." and set references to {}.
6. About idx_range continuity and overlaps:
    - For cases like "... [1][2]", when idx_range for [1] = [5, 10] and for [2] = [10, 15] or = [11, 15], keep only "... [1]" and set idx_range to [5, 15], indicating continuity.
    - The same applies to partial overlap, e.g., if [1] = [5, 10] and [2] = [8, 15], keep "... [1]" and set idx_range to [5, 15].

Output format (JSON):
{
    "answer": "blablabla [1], blablabla [2][3], etc.",
    "references": {
        "1": {"file_id": "<id right after PATH and before the first '>'>", "idx_range": [<start_idx>, <end_idx>]},
        "2": {"file_id": "<id right after PATH and before the first '>'>", "idx_range": [<start_idx>, <end_idx>]},
        ... etc
    }
}

Output must be strict JSON, with no additional text.
"
