dolphinium
commited on
Commit
·
78e7277
1
Parent(s):
30f0de3
prio deal metric values for measure selection
Browse files- llm_prompts.py +4 -3
llm_prompts.py
CHANGED
@@ -85,9 +85,10 @@ This is the most critical part of your task. A bad choice leads to a useless, bo
|
|
85 |
|
86 |
**2. Choosing the `analysis_measure` (The metric):**
|
87 |
|
88 |
-
* **EXPLICIT METRIC:** If the user asks for a value (e.g., "by total deal value"
|
89 |
-
* **IMPLICIT COUNT:**
|
90 |
-
|
|
|
91 |
---
|
92 |
### FIELD DEFINITIONS (Your Source of Truth for Core: {core_name})
|
93 |
|
|
|
85 |
|
86 |
**2. Choosing the `analysis_measure` (The metric):**
|
87 |
|
88 |
+
* **EXPLICIT METRIC:** If the user asks for a value (e.g., "by total deal value," "highest revenue"), use the corresponding field and function (e.g., `sum(total_deal_value_in_million)`).
|
89 |
+
* **IMPLICIT VALUE vs. COUNT:**
|
90 |
+
* **Prioritize Financial Metrics for "Deals":** If the query is about "deals," "financings," or "partnerships," even if the user doesn't explicitly ask for a value (e.g., "show me recent deals"), you **MUST** default to a financial measure like `sum(total_deal_value_in_million)`. The user is always interested in the money behind the deal.
|
91 |
+
* **Use 'count' as a fallback:** For non-financial queries where no metric is specified (e.g., "what are the most common news types?"), 'count' is the appropriate measure.
|
92 |
---
|
93 |
### FIELD DEFINITIONS (Your Source of Truth for Core: {core_name})
|
94 |
|