You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
help="If a text chunk is relevant to the query, then adjacent text chunks in the original document may be able to add additional context to the relevant points. The value of this parameter determines how many chunks before and after each relevant text chunk will be evaluated at the end of the process (or `Relevance test budget`) if they are yet to be tested."
219
219
)
220
220
st.markdown("##### Answer options")
221
-
c1, c2, c3, c4,c5=st.columns(5)
222
-
withc1:
223
-
st.number_input(
224
-
"Target chunks per cluster",
225
-
value=sv.target_chunks_per_cluster.value,
226
-
key=sv.target_chunks_per_cluster.key,
227
-
min_value=0,
228
-
help="The average number of text chunks to target per cluster, which determines the text chunks that will be evaluated together and in parallel to other clusters. Larger values will generally result in more related text chunks being evaluated in parallel, but may also result in information loss from unprocessed content."
Copy file name to clipboardExpand all lines: intelligence_toolkit/query_text_data/prompts.py
+7-2Lines changed: 7 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,7 @@
81
81
- "point_evidence": a paragraph, starting with "**Source evidence**:", describing evidence from sources that support or contradict the point, without additional interpretation
82
82
- "point_commentary": a paragraph, starting with "**AI commentary**:", suggesting inferences, implications, or conclusions that could be drawn from the source evidence
83
83
84
+
Pay attention to previous themes, so don't repeat the same themes or points. If the theme hint is similar to a previous theme, return an empty json object ONLY.
84
85
IMPORTANT: Make theme titles specific and focused to avoid creating duplicate or overlapping themes. If the theme hint suggests a broad category, make your theme title more specific to the actual content found in the sources.
85
86
86
87
--Query--
@@ -91,6 +92,10 @@
91
92
92
93
{theme}
93
94
95
+
--Previous themes--
96
+
97
+
{previous_themes}
98
+
94
99
--Source text chunks--
95
100
96
101
Input text chunks JSON, in the form "<source_id>: <text_chunk>":
@@ -165,11 +170,11 @@
165
170
- Each point MUST contain sufficient concrete details to capture the specific source information only, and not related information
166
171
- If a source relates to an existing point, the source ID MUST be assigned to the existing point ID, rather than creating a new point
167
172
- If the addition of a source to a point warrants a change in point title, the point title MUST be updated
168
-
- Aim for 3-7 themes overall, with an even distribution of points across themes
173
+
- Aim for 2-7 themes overall, with an even distribution of points across themes
169
174
- Points should be assigned to a single theme in a logical sequence that addresses the user query
170
175
- Themes should contain at least two points if possible
171
176
- Order themes in a logical sequence that addresses the user query
172
-
- Output themes need not be the same as input themes and should be regenerated as needed to maintain 3-7 themes overall
177
+
- Output themes need not be the same as input themes and should be regenerated as needed to maintain 2-7 themes overall
173
178
- AVOID creating duplicate or overlapping themes - consolidate similar themes under a single, more comprehensive theme title
174
179
- Before creating a new theme, check if the content could be merged with an existing theme
175
180
- Theme titles should be distinct and non-overlapping - avoid themes that cover the same conceptual territory
0 commit comments