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>
British Army Structure Before Army 2020 The structure of the British Army before the reforms from Army 2020. Overall Structure Commander Land Forces Joint Helicopter Command 1st (United Kingdom) Armoured Division - Operational 'Ready' Division. Brigades based in Germany, headquarters in Herford. 3rd (United Kingdom) Division - Operational 'Reserve Ready' Division. Brigades based throughout the UK. Headquarters in Bulford Theater Troops - Controlled all support brigades and regiments Commander Regional Forces 2nd Division - Regenerative Division based in Northern England, Scotland, and Northern Ireland headquartered in Edinburgh. 4th Division - Regenerative Division based in Southern England, headquartered in Aldershot. 5th Division - Regenerative Division based in Central England, headquartered in Shrewsbury Headquarters London District - Home based command, commands all troops in London and Windsor United Kingdom Support Command (Germany) - Military formation charged with logistics and administration, effectively like a military district. Succeeded by British Forces Germany. Commander Land Forces The forces in Germany were dramatically reduced after the end of the Cold War, but the main force of the army was still in Germany and in 2019-2020 the army will be out of Germany completely. In 1994-2012 United Kingdom Support Command headquarters were in Rheindahlen. 1st (United Kingdom) Armoured Division Operational 'Ready' Division. Brigades based in Germany, headquarters in Herford. 1st Armoured Division Support Group 1st (UK) Armoured Division Headquarters and Signals Regiment, Royal Corps of Signals 1st Regiment, Army Air Corps 12th Regiment, Royal Artillery - Anti-Aircraft Missile Artillery 28th Engineer Regiment, Royal Engineers 1st Military Police Regiment, Royal Military Police - Companies detached to brigades 1st Logistic Support Regiment, Royal Logistic Corps 2nd Logistic Support Regiment, Royal Logistic Corps 4th Mechanized Brigade Headquarters and 204 Signal Squadron, Royal Corps of Signals - Catterick The Queen's Royal Lancers - Armoured Reconnaissance Royal Dragoon Guards - Armoured Scots Guards - Armoured Infantry 1st Battalion, The Duke of Lancaster's Regiment - Armoured Infantry 1st (Cheshire) Battalion, The Mercian Regiment - Light Infantry 4th Regiment, Royal Artillery - Self-Propelled Artillery 21st Engineer Regiment, Royal Engineers 1st Battalion, Royal Electrical and Mechanical Engineers 150 Provost Company, Royal Military Police 7th Armoured Brigade Headquarters and 207 Signal Squadron, Royal Corps of Signals - Hohne 9th/12th Royal Lancers - Armoured Reconnaissance Royal Scots Dragoon Guards - Armoured 1st Battalion, Royal Regiment of Fusiliers - Armoured Infantry 4th (Highlanders (Seaforth, Gordons and Camerons)), Royal Regiment of Scotland - Armoured Infantry 3rd (Staffordshire) Battalion, The Mercian Regiment - Armoured Infantry 3rd Regiment Royal Horse Artillery - Self-Propelled Artillery 32nd Engineer Regiment, Royal Engineers 2nd Battalion, Royal Electrical and Mechanical Engineers 20th Armoured Brigade Headquarters and 200 Signal Squadron, Royal Corps of Signals - Paderborn Queen's Dragoon Guards - Armoured Reconnaissance Queen's Royal Hussars - Armoured 1st Battalion, The Princess of Wales' Own Regiment - Armoured Infantry 5th Battalion, The Rifles - Mechanized Infantry 1st (Prince of Wales's Own) Battalion, The Yorkshire Regiment - Light Infantry 26th Regiment, Royal Artillery - Self-Propelled and MLRS Artillery 35th Engineer Regiment, Royal Engineers 3rd Battalion, Royal Electrical and Mechanical Engineers 102nd Logistic Brigade Headquarters and 262 Signal Squadron, Royal Corps of Signals 6th Regiment, Royal Logistic Corps 7th Regiment, Royal Logistic Corps 8th Regiment, Royal Logistic Corps 101st Battalion, Royal Electrical and Mechanical Engineers 5th Regiment, Royal Military Police 5th Medical Regiment, Royal Army Medical Corps 102 Military Working Dog Squadron, Royal Army Veterinary Corps 103 Military Working Dog Squadron, Royal Army Veterinary Corps 105 Military Working Dog Squadron, Royal Army Veterinary Corps 3rd (United Kingdom) Division 'Operational Maneuver' Division. Brigades based throughout the UK. Headquarters in Bulford 3rd Mechanized Division Support Group 3rd (UK) Division Headquarters and Signal
</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.