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>
Southwestern Istrian Southwestern Istrian dialect (), also known as Chakavian-Shtokavian/Shtokavian-Chakavian/Shtakavian-Chakavian ikavian dialect (), is one of the subdialects of the Chakavian dialect in Istria, Croatia.<ref name="LisacDijalekt2009">Josip Lisac, Hrvatska dijalektologija 2: Čakavsko narječje", 2009, Golden marketing / Tehnička knjiga, str. 51-72.</ref> Through the history there were different hypothesis which classified it, beside the Chakavian dialect, also to Shtokavian dialect, because it is a transitional dialect.Josip Lisac, Nastanak i razvoj jugozapadnoga istarskog dijalekta, 2003, časopis Nova Istra, br. 8Lina Pliško, Jugozapadni istarski ili štakavsko-čakavski dijalekt u svjetlu Hrastina istraživanja, 2009, Hrvatski dijalektološki zbornik, br. 15, str. 111-124 It is the most widespread Chakavian subdialect in Istria. Origin and history The subdialect is a mixture of Chakavian and Shtokavian elements. It is considered that it emerged in Istria after the 16th-century migration of speakers who originated from Dalmatia, mainly from the hinterland of Makarska Riviera where mostly was spoken Shtokavian dialect of Ikavian pronunciation with Chakavian characteristics, which with emigration and consolidation of speakers on the Šibenik-Zadar territory assimilated additional Chakavian elements. It is considered that the place of origination was not situated at the sea, but also not very far from it. The emigration was caused by the Ottoman conquest of Western Balkans, and immigration in Istria was conducted by Venice Republic due to poor population density after late medieval de-population of the peninsula. It is argued that the territory around Zadar (Ravni Kotari) was only an intermediate station for the migration to Istria. To this subdialect is related Slavomolisano dialect of Molise Croats from Zabiokovlje, although it has less Chakavian elements. In different territories there exist different dialects transitions and boundaries, and with its origination from Dalmatian-Herzegovinian region in which initially prevailed Shtokavian elements while later and present-day Chakavian elements, it can be considered as a postmigrational or transitional subdialect. According to the linguist Josip Ribarić, the Chakavian elements cannot be interpreted with the neighborhood of native Chakavian speakers in Istria because Northern Chakavian subdialect does not have these elements, and as such in the Southwestern Istrian dialect was "saved reflection of the Shtokavian-Chakavian dialect spoken at the end of the 15th, during the 16th and the first half of the 17th century spoke on the Dalmatian mainland". According to philologist Lina Pliško, "the main language layer features Ikavian Chakavian from Zadar hinterland, but were also preserved features of assimilated Ikavian Štakavian speakers originating from Makarska (Podbiokovlje) region, who arrived to Istria in a migrational wave with Ikavian Chakavian speakers, and in more-or-less number also language features of Ekavian Chakavian speakers (Northern Chakavian, Buzet, and partly Middle Chakavian subdialect). The subdialect was first mentioned by Ribarić in 1916. In the second half of the 20th century, to the dialect was attributed a larger number of Shtokavian elements and hence was also classified among Shtokavian Ikavian subdialects, a thesis first argued by Polish linguist Mieczysław Małecki (1930), which was mostly supported by Serbian linguists, Aleksandar Belić, Pavle Ivić and Radosav Bošković. However, a comprehensive research made by Mate Hraste in 1964 held for determination of Shtokavian languages in Istria found that Southwestern Istria "is not Shtokavian nor Shtokavian-Chakavian, as was called by Ribarić, but Chakavian-Shtokavian, because in it even today prevail Chakavian elements, and not Shtokavian. Shtokavian is only Premantura, Banjole, Vintijan, Vinkuran and Valdebek, although even in those places there are Čakavian adstrata which was introduced from the hinterland during the centuries to the present day. The language of all these places even today is mostly Chakavian". According to it, and work by Dalibor Brozović, Ivić in 1981 argued that if the subdialect is classified among Chakavian subdialects it belongs to
</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.