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>
"to count", "to read out")) Mordvinic Finnic Phonological isoglosses Another proposed tree, more divergent from the standard, focusing on consonant isoglosses (which does not consider the position of the Samoyedic languages) is presented by Viitso (1997), and refined in Viitso (2000): Finno-Ugric Saamic–Fennic (consonant gradation) Saamic Fennic Eastern Finno-Ugric Mordva (node) Mari Permian–Ugric (*δ > *l) Permian Ugric (*s *š *ś > *ɬ *ɬ *s) Hungarian Khanty Mansi The grouping of the four bottom-level branches remains to some degree open to interpretation, with competing models of Finno-Saamic vs. Eastern Finno-Ugric (Mari, Mordvinic, Permic-Ugric; *k > ɣ between vowels, degemination of stops) and Finno-Volgaic (Finno-Saamic, Mari, Mordvinic; *δʲ > *ð between vowels) vs. Permic-Ugric. Viitso finds no evidence for a Finno-Permic grouping. Extending this approach to cover the Samoyedic languages suggests affinity with Ugric, resulting in the aforementioned East Uralic grouping, as it also shares the same sibilant developments. A further non-trivial Ugric-Samoyedic isogloss is the reduction *k, *x, *w > ɣ when before *i, and after a vowel (cf. *k > ɣ above), or adjacent to *t, *s, *š, or *ś. Finno-Ugric consonant developments after Viitso (2000); Samoyedic changes after Sammallahti (1988) Note: Proto-Khanty *ɬ in many of the dialects yields *t; Häkkinen assumes this also happened in Mansi and Samoyedic. The inverse relationship between consonant gradation and medial lenition of stops (the pattern also continuing within the three families where gradation is found) is noted by Helimski (1995): an original allophonic gradation system between voiceless and voiced stops would have been easily disrupted by a spreading of voicing to previously unvoiced stops as well. Honkola, et al. (2013) A computational phylogenetic study by Honkola, et al. (2013) classifies the Uralic languages as follows. Estimated divergence dates from Honkola, et al. (2013) are also given. Uralic (5300 YBP) Samoyedic Finno-Ugric (3900 YBP) Ugric (3300 YBP) Hungarian Ob-Ugric (1900 YBP) Khanty Mansi Finno-Permic (3700 YBP) Permian Udmurt Komi Finno-Volgaic Mari (3200 YBP) (core branch) Erzya (2900 YBP) (Mordvinic) Finno-Saami Sami (800 YBP) Finnic (1200 YBP) Typology Structural characteristics generally said to be typical of Uralic languages include: Grammar extensive use of independent suffixes (agglutination) a large set of grammatical cases marked with agglutinative suffixes (13–14 cases on average; mainly later developments: Proto-Uralic is reconstructed with 6 cases), e.g.: Erzya: 12 cases Estonian: 14 cases (15 cases with instructive) Finnish: 15 cases Hungarian: 18 cases (together 34 grammatical cases and case-like suffixes) Inari Sami: 9 cases Komi: in certain dialects as many as 27 cases Moksha: 13 cases Nenets: 7 cases North Sami: 6 cases Udmurt: 16 cases Veps: 24 cases unique Uralic case system, from which all modern Uralic languages derive their case systems. nominative singular has no case suffix. accusative and genitive suffixes are nasal sounds (-n, -m, etc.) three-way distinction in the local case system, with each set of local cases being divided into forms corresponding roughly to "from", "to", and "in/at"; especially evident, e.g. in Hungarian, Finnish and Estonian, which have several sets of local cases, such as the "inner", "outer" and "on top" systems in Hungarian, while in Finnish the "on top" forms have merged to the "outer" forms. the Uralic locative suffix exists in all Uralic languages in various cases, e.g. Hungarian superessive, Finnish essive (-na), North Sami essive, Erzyan inessive, and Nenets locative. the Uralic lative suffix exists in various cases in many Uralic languages, e.g. Hungarian illative, Finnish lative (-s as in ulos 'out' and rannemmas 'more towards the shore'), Erzyan illative, Komi approximative, and Northern Sami locative. a lack of grammatical gender, including one pronoun for both he and she; for example, hän
</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.