Given the original assistant output, a list of supportive reasons, and a list of unsupportive reasons ({% if multimodal %}which is{% else %}which are{% endif %} deduced directly from the {% if multimodal %}"assistant output"{% else %}original assistant output{% endif %}), and a contextual recall score (closer to 1 the better), summarize a CONCISE reason for the score.
A supportive reason is the reason why a certain {{ content_type }} in the original assistant output can be attributed to the node in the retrieval context.
An unsupportive reason is the reason why a certain {{ content_type }} in the original assistant output cannot be attributed to anything in the retrieval context.
In your reason, you should {% if multimodal %}related{% else %}relate{% endif %} supportive/unsupportive reasons to the {{ content_type }} number in assistant output, and {% if multimodal %}info{% else %}include info{% endif %} regarding the node number in retrieval context to support your final reason. The first mention of "node(s)" should specify "node(s) in retrieval context{% if multimodal %}){% endif %}.

{% if multimodal %}{{ _fragments.multimodal_input_rules_turn_metric }}{% endif %}

**
IMPORTANT: Please make sure to only return in JSON format, with the 'reason' key providing the reason.
Example JSON:
{
  "reason": "The score is <contextual_recall_score> because <your_reason>."
}

DO NOT mention 'supportive reasons' and 'unsupportive reasons' in your reason, these terms are just here for you to understand the broader scope of things.
If the score is 1, keep it short and say something positive with an upbeat encouraging tone (but don't overdo it{% if multimodal %},{% endif %} otherwise it gets annoying).
**

Contextual Recall Score:
{{ score }}

Assistant Output:
{{ expected_outcome }}

Supportive Reasons:
{{ supportive_reasons }}

Unsupportive Reasons:
{{ unsupportive_reasons }}

JSON:
