Spaces:
Runtime error
Runtime error
Update app.py
Browse files
app.py
CHANGED
|
@@ -1212,6 +1212,7 @@ Keep in mind the:
|
|
| 1212 |
// Critical Requirements
|
| 1213 |
- It MUST include inline citations using the format [1], [2], etc., that exactly match the reference numbering used in the overall report.
|
| 1214 |
Note: no need to add a reference table at the end of the focus box, all the references / citations have already been listed at the end of the report (just refer to the [x] provided in the placeholder instructions)
|
|
|
|
| 1215 |
- Use html with css to render it, keep it sober and focused on the content
|
| 1216 |
- The output has to be boxed in a border of 1px Black
|
| 1217 |
- Font size minimum 12px for readability in PDF
|
|
@@ -1221,14 +1222,14 @@ Note: no need to add a reference table at the end of the focus box, all the refe
|
|
| 1221 |
// Mentioning sources, organisations and individuals
|
| 1222 |
- We will perform a post-processing on the output to remove all the identifiable organisations, people and projects
|
| 1223 |
- For this reasons use this format for any specific name, organisation or project: {{[{{name}}]}}
|
| 1224 |
-
ex1: {{[{{Google}}]}} CEO, {{[{{Sundar Pichai}}]}} ...
|
| 1225 |
ex2: in a report from the {{[{{university of Berkeley}}]}} titled "{{[{{The great acceleration}}]}}"...
|
| 1226 |
-
ex3:
|
| 1227 |
ex4: the project {{[{{Stargate}}]}}, anounced by {{[{{OpenAI}}]}} in collaboration with {{[{{Salesforce}}]}}
|
| 1228 |
ex5: Mr. {{[{{Michael Parrot}}]}}, Marketing director in {{[{{Panasonic}}]}}, mentioned that ...
|
| 1229 |
Note: the output will be processed through regex and the identifiers removed, but this way we can keep track of all sources and citations without disclosing them.
|
| 1230 |
- This should apply to names, people/titles, dates, papers, reports, organisation/institute/NGO/government bodies quotes, products, project names, ...
|
| 1231 |
-
Important: you
|
| 1232 |
|
| 1233 |
// Important
|
| 1234 |
- Make it real, with anecdotes from the content
|
|
@@ -1476,9 +1477,9 @@ Instructions:
|
|
| 1476 |
1. Relevance: Determine if the content is relevant to the research topic. Answer with a single word: "yes" or "no".
|
| 1477 |
|
| 1478 |
2. Structure: If the content is relevant, provide a comprehensive summary structured into the following sections. Prioritize extreme conciseness and token efficiency while preserving all key information. Aim for the shortest possible summary that retains all essential facts, figures, arguments, and quotes. The total summary should not exceed 1000 words, but shorter is strongly preferred.
|
| 1479 |
-
- Key Facts (at least
|
| 1480 |
-
- Key Figures (at least
|
| 1481 |
-
- Key Arguments (at least 5): Identify main arguments or claims. Summarize supporting evidence and counter-arguments concisely.
|
| 1482 |
- Key Quotes (at least 1 if any): Include significant quotes (with the author's name in parenthesis). Attribute quotes correctly. Paraphrase if needed, indicating that it's a paraphrase. Use symbols (e.g., &, +, ->, =) to conserve tokens.
|
| 1483 |
- Structured Summary (10 to 50 sentences): Provide a structured summary that includes anecdotes, people, and locations to ensure the report is relatable.
|
| 1484 |
|
|
@@ -1668,7 +1669,7 @@ Note: This is for academic purposes, so thorough citations and referencing are e
|
|
| 1668 |
Note: put the full reference url (no generic domain address), down to the html page or the pdf
|
| 1669 |
5. It must follow this writing style {reportstyle}.
|
| 1670 |
|
| 1671 |
-
// Mentioning sources, organisations and individuals
|
| 1672 |
- We will perform a post-processing on the output to remove all the identifiable organisations, people and projects
|
| 1673 |
- For this reasons use this format for any specific name, organisation or project: {{[{{name}}]}}
|
| 1674 |
ex1: {{[{{Google}}]}} CEO, {{[{{Sundar Pichai}}]}} ...
|
|
@@ -1678,7 +1679,7 @@ ex4: the project {{[{{Stargate}}]}}, anounced by {{[{{OpenAI}}]}} in collaborati
|
|
| 1678 |
ex5: Mr. {{[{{Michael Parrot}}]}}, Marketing director in {{[{{Panasonic}}]}}, mentioned that ...
|
| 1679 |
Note: the output will be processed through regex and the identifiers removed, but this way we can keep track of all sources and citations without disclosing them.
|
| 1680 |
- This should apply to names, people/titles, dates, papers, reports, organisation/institute/NGO/government bodies quotes, products, project names, ...
|
| 1681 |
-
Important: you
|
| 1682 |
|
| 1683 |
// Sources
|
| 1684 |
Use the following learnings and merged reference details from a deep research process on:
|
|
@@ -1693,6 +1694,7 @@ If you cannot produce a high level of details for specific topic or section, put
|
|
| 1693 |
// Requirements
|
| 1694 |
- All text alignment has to be on the left
|
| 1695 |
- It must include inline citations (e.g., [1], [2], etc.) from real sources provided in the search results below
|
|
|
|
| 1696 |
- Do not add any inline citations reference in the placeholders descriptions below (visual, graph), you can add them in focus though.
|
| 1697 |
- No more than 7 sentences per div blocks, skip lines and add line breaks when changing topic.
|
| 1698 |
- The report must include between {round(pages/3.3,0)} and {round(pages/2,0)} tables from the sources used (add citations if necessary) and use facts and figures extensively to ground the analysis.
|
|
|
|
| 1212 |
// Critical Requirements
|
| 1213 |
- It MUST include inline citations using the format [1], [2], etc., that exactly match the reference numbering used in the overall report.
|
| 1214 |
Note: no need to add a reference table at the end of the focus box, all the references / citations have already been listed at the end of the report (just refer to the [x] provided in the placeholder instructions)
|
| 1215 |
+
Note2: citations sources in-line need to be in this format: blablabla - Source [x] / "pdf" is not a source, provide the title or author
|
| 1216 |
- Use html with css to render it, keep it sober and focused on the content
|
| 1217 |
- The output has to be boxed in a border of 1px Black
|
| 1218 |
- Font size minimum 12px for readability in PDF
|
|
|
|
| 1222 |
// Mentioning sources, organisations and individuals
|
| 1223 |
- We will perform a post-processing on the output to remove all the identifiable organisations, people and projects
|
| 1224 |
- For this reasons use this format for any specific name, organisation or project: {{[{{name}}]}}
|
| 1225 |
+
ex1: {{[{{Google}}]}}'s CEO, {{[{{Sundar Pichai}}]}} ...
|
| 1226 |
ex2: in a report from the {{[{{university of Berkeley}}]}} titled "{{[{{The great acceleration}}]}}"...
|
| 1227 |
+
ex3: {{[{{Softbank}}]}}'s CEO , {{[{{Masayoshi Son}}]}}, said that "the best way to..."
|
| 1228 |
ex4: the project {{[{{Stargate}}]}}, anounced by {{[{{OpenAI}}]}} in collaboration with {{[{{Salesforce}}]}}
|
| 1229 |
ex5: Mr. {{[{{Michael Parrot}}]}}, Marketing director in {{[{{Panasonic}}]}}, mentioned that ...
|
| 1230 |
Note: the output will be processed through regex and the identifiers removed, but this way we can keep track of all sources and citations without disclosing them.
|
| 1231 |
- This should apply to names, people/titles, dates, papers, reports, organisation/institute/NGO/government bodies quotes, products, project names, ...
|
| 1232 |
+
Important: you will safely mention any of these elements provided you respect the above mentioned formatting {{[{{...}}]}}, you must have at least 20 of such occurences
|
| 1233 |
|
| 1234 |
// Important
|
| 1235 |
- Make it real, with anecdotes from the content
|
|
|
|
| 1477 |
1. Relevance: Determine if the content is relevant to the research topic. Answer with a single word: "yes" or "no".
|
| 1478 |
|
| 1479 |
2. Structure: If the content is relevant, provide a comprehensive summary structured into the following sections. Prioritize extreme conciseness and token efficiency while preserving all key information. Aim for the shortest possible summary that retains all essential facts, figures, arguments, and quotes. The total summary should not exceed 1000 words, but shorter is strongly preferred.
|
| 1480 |
+
- Key Facts (at least 10, if present): List the core factual claims using short, declarative sentences or bullet points. Apply lemmatization and standard abbreviations.
|
| 1481 |
+
- Key Figures (at least 10, if present): Extract numerical data (statistics, dates, percentages) and include any necessary context (units, references, explanations) required to interpret these numbers. Present them concisely (list or table format).
|
| 1482 |
+
- Key Arguments (at least 5, if present): Identify main arguments or claims. Summarize supporting evidence and counter-arguments concisely.
|
| 1483 |
- Key Quotes (at least 1 if any): Include significant quotes (with the author's name in parenthesis). Attribute quotes correctly. Paraphrase if needed, indicating that it's a paraphrase. Use symbols (e.g., &, +, ->, =) to conserve tokens.
|
| 1484 |
- Structured Summary (10 to 50 sentences): Provide a structured summary that includes anecdotes, people, and locations to ensure the report is relatable.
|
| 1485 |
|
|
|
|
| 1669 |
Note: put the full reference url (no generic domain address), down to the html page or the pdf
|
| 1670 |
5. It must follow this writing style {reportstyle}.
|
| 1671 |
|
| 1672 |
+
// Mentioning sources, organisations and individuals in safe format
|
| 1673 |
- We will perform a post-processing on the output to remove all the identifiable organisations, people and projects
|
| 1674 |
- For this reasons use this format for any specific name, organisation or project: {{[{{name}}]}}
|
| 1675 |
ex1: {{[{{Google}}]}} CEO, {{[{{Sundar Pichai}}]}} ...
|
|
|
|
| 1679 |
ex5: Mr. {{[{{Michael Parrot}}]}}, Marketing director in {{[{{Panasonic}}]}}, mentioned that ...
|
| 1680 |
Note: the output will be processed through regex and the identifiers removed, but this way we can keep track of all sources and citations without disclosing them.
|
| 1681 |
- This should apply to names, people/titles, dates, papers, reports, organisation/institute/NGO/government bodies quotes, products, project names, ...
|
| 1682 |
+
Important: you will safely mention any of these provided you respect the above mentioned formatting {{[{{...}}]}}, you must have at least {10 * pages} of such occurences scattered around the report.
|
| 1683 |
|
| 1684 |
// Sources
|
| 1685 |
Use the following learnings and merged reference details from a deep research process on:
|
|
|
|
| 1694 |
// Requirements
|
| 1695 |
- All text alignment has to be on the left
|
| 1696 |
- It must include inline citations (e.g., [1], [2], etc.) from real sources provided in the search results below
|
| 1697 |
+
Note: citations sources in-line need to be in this format: blablabla - Source [x] / "pdf" is not a source, provide the title or author
|
| 1698 |
- Do not add any inline citations reference in the placeholders descriptions below (visual, graph), you can add them in focus though.
|
| 1699 |
- No more than 7 sentences per div blocks, skip lines and add line breaks when changing topic.
|
| 1700 |
- The report must include between {round(pages/3.3,0)} and {round(pages/2,0)} tables from the sources used (add citations if necessary) and use facts and figures extensively to ground the analysis.
|