Update README.md

README.md

@@ -68,7 +68,49 @@ Title: {document_title}
 Question: {question}
 Passage: {context_passage}
 
-[QED instruction prompt requesting JSON output...]
+You are an expert at extracting answers and structured explanations from text.
+Your response MUST be **valid JSON only** (no extra commentary).
+
+Task
+====
+Given:
+• a **title** for the passage,
+• a **question** about the passage, and
+• the **context passage** itself,
+
+produce an explanation object with three parts:
+
+1. "answer" – the **shortest span** from the passage that fully answers the question.
+2. "selected_sentence" – the **single sentence** in the passage that entails or implies the answer.
+3. "referential_equalities" – a list of mappings between phrases in the question and phrases in the selected sentence
+   that refer to the **same real-world entity/event**.
+
+   • Each mapping has two keys:
+       - "question_reference": the exact phrase from the question (**must be a contiguous substring from the question,
+          not from the context or title**).
+       - "sentence_reference": the exact phrase from the selected sentence (**must be a contiguous substring from the selected sentence,
+          not from the question or title**), or "" (empty string if the entire sentence is the referent).
+
+     ▸ Use **""** for "sentence_reference" when the entity/event is not named by any specific phrase in the sentence –
+       i.e. the entire sentence acts as the referent (a *bridge* to the whole sentence).  
+       This corresponds to the (start = end = -1) convention in the QED dataset.
+
+Output format
+=============
+Return **only** JSON in this exact schema:
+
+{
+  "answer": "<string from passage>",
+  "selected_sentence": "<string from passage>",
+  "referential_equalities": [
+    {
+      "question_reference": "<string from question only>",
+      "sentence_reference": "<string from selected_sentence only, or "">",
+      "bridge": "<false if not a bridge; otherwise, a string explaining the bridge connection, e.g., 'in', 'for', 'of', 'at', 'on'>"
+    }
+    ...
+  ]
+}
 """
 
 # Model outputs structured explanations in JSON format