You are an AI assistant tasked with analyzing a passage of text to insert retrieval tokens and identify Prefix-intent (PI) and Key Factual Information (KFI). A Prefix-Intent (PI) should be a piece of text that should precede factual information, it must not be only 1 or 2 words. Key Factual Information (KFI) should be meaningful and include important details.

Your goal is to insert a  <|retrieval|> token after it is clear what the intent of the text is (e.g., "The president of the USA is"), but  before the key factual information is stated (e.g., "Joe Biden"). Whenever there is a <|retrieval|> token, we will retrieve the key factual information.

Here is the passage you will be working with:

<passage>
2006 that put the death toll in the war at 8 to 10 million. An academic study of the Chinese population concluded that "a conservative estimate would put total human casualties directly caused by the war of 1937–1945 at between 15,000,000 and 20,000,000" This study cited a Chinese Nationalist source that put total civilian casualties at 2,144,048 =(1,073,496 killed; 237,319 wounded; 71,050 captured by Japanese; 335,934 killed in Japanese air raids; 426,249 wounded in air raids), military casualties at 6,750,000 in 1937–1943 (1,500,000 killed; 3,000,000 wounded; 750,000 missing; 1,500,000 deaths caused by sickness, etc. In addition 960,000 collaborator forces and 446,736 Communist were killed or wounded The official Chinese government (communist) statistic for China's civilian and military casualties in the Second Sino-Japanese War in 1937–1945 is 20 million dead and 15 million wounded. Chinese scholar Bianxiu Yue has published a study of China's population losses in the Second Sino-Japanese War . He put total Chinese losses at 20.6 million dead and 14.2 million injured. Official Nationalist Chinese casualty figures were: killed 1,319,958; wounded 1,716,335 and missing 130,126, An academic study of the Chinese population concluded that these figures are "unreasonably low" and "highly suspect" R. J. Rummel's estimate of total war dead in 1937–45 is 19,605,000. Military dead: 3,400,000 (including 400,000 POW) Nationalist/Communist, and 432,000 collaborator forces.Civilian war deaths: 3,808,000 killed in fighting and 3,549,000 victims of Japanese war crimes (not including an additional 400,000 POWs).Other deaths: Repression by Chinese Nationalists 5,907,000 (3,081,000 military conscripts who died due to mistreatment and 2,826,000 civilian deaths caused by Nationalist government, including the 1938 Yellow River flood); political repression by Chinese Communists 250,000 and by Warlords 110,000. Additional deaths due to famine were 2,250,000. Werner Gruhl estimates China's total war losses at 15,554,000, Civilians :12,392,000 including (8,191,000) due to the Japanese brutality and military dead 3,162,000. Cuba Cuba lost 5 merchant ships and 79 dead merchant mariners. Czechoslovakia According to the Czechoslovak State Statistical Office the population at 1/1/1939 (within post war 1945–1992 borders) was 14,612,000. The population in 1939 included about 3.3 million ethnic Germans that were expelled after the war or were German military casualties during the war. Russian demographer Boris Urlanis estimated Czechoslovak war dead of 340,000 persons, 46,000 military and 294,000 civilians. A Russian historian in a handbook of human losses in the 20th century has provided the following assessment of Czechoslovak casualties: 35,000 Military deaths: including: killed during 1938 occupation (171); Czechoslovak Forces with the Western Allies (3,220); Czechoslovak military units on Eastern front (4,570); Slovak Republic Axis forces (7,000); Czechs in German forces (5,000), partisan losses 10,000 and (5,000) POWs.320,000 Civilian deaths: (10,000) in bombing and shelling; (22,000) executed; (285,000 in camps including 270,000 Jews, 8,000 Roma); and (3,000) forced laborers in Germany. Denmark The Danish Ministry of Education has detailed Denmark's losses in the war of about 8,000 persons including 2,685 killed in Denmark in bombing raids, resistance fighters and those executed by the Germans and 3,000 who died outside Denmark including (2,000 merchant seamen, 63 serving with Allied forces, 600 in German camps, 400 workers in Germany). In addition 2,000 Danish volunteers were killed serving in the Germany military. Dutch East Indies The United Nations reported in 1947 that "about 30,000 Europeans and 300,000 Indonesian internees and forced laborers died during the occupation." They reported, "The total number who were killed by the Japanese, or who died from, hunger, disease and lack of medical attention is estimated at 3,000,000 for Java alone, 1,000,000 for the Outer Islands. Altogether 35,000 of the 240,000 Europeans died; most of them were men of working age." John W. Dower
</passage>

Follow these steps to complete the task:

1. Inserting retrieval tokens:
   a. Read through the text carefully.
   b. Identify potential Prefix-Intent (PI) sections that consist of a single intent and could serve as a search query. You must not modify the prefix intent and it MUST be part verbatim in the passage. It cannot be single or only a few words.
   c. For each identified PI, evaluate if the following sentence/subsentece that could serve as Key Factual Information (KFI).
   d. Insert <|retrieval|> tokens into the text AFTER the Prefix Intent (PI) and BEFORE key factual information is stated (KFI).
   e. Key Factual information should not intersect with Prefix Intent.

2. Identifying Prefix-Intent (PI) and Key Factual Information (KFI):
   a. For each <|retrieval|> token you've inserted, identify the preceding text as the Prefix-Intent (PI).
   b. Identify the following text, up to the next PI, as the Key Factual Information (KFI).
   c. Ensure that both PI and FI are short subsentences or phrases but not 1 or 2 words.

3. Insert <|start-PI|>,<|end-PI|>, <|start-KFI|>, <|end-KFI|>.
   a. For each identified Prefix Intent (PI), add a start and end special tokens (<|start-PI|>,<|end-PI|>) to quickly identify them.
   b. Do the same for the Key Factual Information (KFI) (<|start-KFI|>, <|end-KFI|>)
   c. Ensure that the very first PI in the passage is preceded by <|start-PI|>.
   d. Double-check that every PI and KFI is properly enclosed in these tags.

4. Describing ideal retrieved information:
   a. Given the Prefix-Intent (PI) and Key Factual Information (KFI), imagine an ideal retriever and enormous corpus. 
   b. Using the retriever and corpus, imagine that you can retrieve information given the Prefix-Intent.  
   c. Describe how that content should look like so it helps generating the Key Factual Information (KFI)


5. Reformulate the Prefix Intent if necessary: Reformulate it to not be impersonal. This means that if the subject it is not identified (e.g. it, he, she) you need to add the appropriate subject so the prefix-intent can be understood by itself. The subject should be changed from the previous information in the passage. Reformulated Prefix should not add any extra information or intent that is not mentioned in the original Prefix Intent.


6. Output format:
   For each pair of Prefix-Intent (PI) and Key Factual Information (KFI) you identify, provide the following output separating each example in a JSON list output. Ensure that it is actually a JSON.

   - Prefix_intent: [Write the Prefix Intent here]
   - Prefix_reformulated: [Write the Prefix Intent reformulated]
   - Key_Factual_Information: [Write the Key Factual Information here]
   - Verification: [Confirm that the KFI can be directly derived from the PI given a strictly connected context]
   - Ideal_Knowledge: [Describe how the ideal retrieved content should look to generate the KFI]
   - Explanation: [Briefly explain how the PI and KFI connect and why you chose to insert the <|retrieval|> token in that position]


7. Final step:
   After you have completed the analysis and provided outputs for all identified PI-KFI pairs, present the original passage with the <|retrieval|> tokens inserted in their appropriate positions

Here's an example of the expected output format:

Passage: Girmal Falls General This waterfall extends to a height of up to 100 feet, making it the highest waterfall of Gujarat. The picturesque beauty of this site makes it popular among visitors and people of the region alike. The water swiftly falls from a great height, creating a fog like condition that’s eye catching. The government of this state is working on many projects to make this place an ideal picnic spot and a tourist attraction. The fall comes to its best form at the time of monsoon and provides an immensely striking appearance. Some of the best natural features of Gujarat can be explored in this place. This place is a nice and refreshing retreat for any traveler.

```json
{ "results" : [
  {
    "Prefix_intent": "Girmal Falls General This waterfall extends to a height of up to",
    "Prefix_reformulated": "What is the height of Girmal Falls?",
    "Key_Factual_Information": "100 feet, making it the highest waterfall of Gujarat",
    "Verification": "The KFI directly provides the height information requested in the PI.",
    "Ideal_Knowledge": "A list of waterfalls in Gujarat, India, with their heights and rankings, specifically mentioning Girmal Falls as the highest at 100 feet.",
    "Explanation": "The PI introduces Girmal Falls and sets up a query about its height, while the KFI provides the specific measurement and its significance. The <|retrieval|> token is inserted to indicate where additional information might be needed to support the factual statement."
  },
  {
    "Prefix_intent": "The water swiftly falls from a great height, creating",
    "Prefix_reformulated": "What does the water falling from Girmal Falls create?",
    "Key_Factual_Information": "a fog like condition that's eye catching",
    "Verification": "The KFI directly describes the effect created by the falling water, as prompted by the PI.",
    "Ideal_Knowledge": "Detailed descriptions of the visual effects created by high waterfalls, including the formation of mist or fog-like conditions due to water droplets in the air.",
    "Explanation": "The PI describes the water falling and sets up a query about its effect, while the KFI provides the specific visual phenomenon created. The <|retrieval|> token is inserted to indicate where additional information might be needed to support the description."
  },
  {
    "Prefix_intent": "The fall comes to its best form at the time of",
    "Prefix_reformulated": "When does Girmal Falls come to its best form?",
    "Key_Factual_Information": "monsoon and provides an immensely striking appearance",
    "Verification": "The KFI directly answers when the waterfall is at its best and describes its appearance, as prompted by the PI.",
    "Ideal_Knowledge": "Information on the seasonal variations of Girmal Falls, highlighting the monsoon season's impact on water flow and visual appeal.",
    "Explanation": "The PI sets up a query about the best time to view the falls, and the KFI provides the specific season and describes the appearance. The <|retrieval|> token is inserted to indicate where additional information about seasonal changes might be needed."
  }],
"Updated_Passage":"<|start-PI|> Girmal Falls General This waterfall extends to a height of up to <|end-PI|> <|retrieval|> <|start-KFI|> 100 feet, making it the highest waterfall of Gujarat <|end-KFI|>. The picturesque beauty of this site makes it popular among visitors and people of the region alike. <|start-PI|> The water swiftly falls from a great height, creating <|end-PI|> <|retrieval|> <|start-KFI|> a fog like condition that’s eye catching <|end-KFI|>. The government of this state is working on many projects to make this place an ideal picnic spot and a tourist attraction. <|start-PI|> The fall comes to its best form at the time of <|end-PI|> <|retrieval|> <|start-KFI|> monsoon and provides an immensely striking appearance <|end-KFI|>. Some of the best natural features of Gujarat can be explored in this place. This place is a nice and refreshing retreat for any traveler."
}

```
8. Final check:
  a. Review the Updated_Passage to ensure all PIs and KFIs are properly tagged.
  b. Verify that the first PI in the passage starts with <|start-PI|>.
  c. Make sure there are no missing or misplaced tags.
 
Remember to analyze the entire passage, identify all relevant PI-KFI pairs, and provide the output for each pair as specified. After completing the analysis, present the original passage with the <|retrieval|> tokens inserted in their appropriate positions as part of a new key in the JSON file. Only Ouput the JSON File.