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>
| 24 | 0 | 0 | 1 | 32 |240 W |- | 8132F | 0 | 24 | 0 | 1 | 32 |176 W |- | 8164 | 48 | 0 | 2 | 1 | 64 |395 W |- | 8164F | 0 | 48 | 2 | 1 | 64 |220 W |} Up to 6 units in the 8100 series can be stacked to form one logical switch and any type of interface (10Gb or 40Gb, fiber-optical or utp copper) can be used for stacking. Similar to the rack-switches PCT7000 and PCT8024 series the switch offers an out-of-band'' fast-ethernet port for management as well as a serial console connection, required for initial configuration. The switch is built around the Broadcom Trident+ ASIC: the same ASIC as can be found in Cisco Nexus 5000 switches or Force10 models. The PowerConnect 8100 is initially released with firmware 5.0 of the switch-firmware which offers the same features as the PowerConnect 7000 and 8024 rack-switches and the different M-series ethernet switches. The underlying operating system of the PCT8100 is based on Linux 2.6 where all other 'Broadcom powered' PowerConnects run on VxWorks. ` Dell Networking H series The Dell Networking H-series is really an OEM version of Intels' Omni-Path platform, which itself is an alternative for InfiniBand. When managing an OmniPath network many commands are very similar to Infiniband switches. Dell Networking N series The N-series switches come in 3 groups: N1500: Gigabit layer2 switches The N1500 offers a low budget step in model compared to the N2000. The N1500 doesn't have dedicated (back-side) stacking-ports but you can convert 10G ethernet uplink ports to stacking-ports and stack multiple N1500's together. N2000: Gigabit layer2 switches The N2000 is an Ethernet switch with limited IP capabilities. There are two 'sizes': 24 x 1GbaseT or 48 x 1GBaseT ports and each of them available as POE+ or standard switch. All models in the N20xx series can be stacked with other models in the same series. Although they do use same stacking-cables as the N3000 series it is NOT possible to stack N2000 with N3000 switches. All models come with 2 x 10Gbase SFP+ uplink ports and two 'twentigig' stacking ports at the back. Management can be done by assigning IP address to switch or one of the vlan-interfaces. The N2000 is marketed as the follow-up for the legacy PowerConnect 5500 models as well as the Force10 S25 and S50 models. It is also possible to convert a N2000 series switch to a port-externder for the new C9010 platform. A N2048P would then have exact same features as the 'standard' C1048P port-extender: but for other port-numbers or when you want NO POE support you can convert N2000 switches to port-extenders. But the main reason to do it is to avoid losing investment in your N-series access-platform when moving to the C9010 chassis-based platform with one single point of management. N3000: Gigabit multi-layer switches The N3000 is hardware-wise pretty similar to the N2000 series but the OS offers advanced IP capabilities (including routing protocols like RIP, OSPF, PBR etc.). Besides the 4 model choices as in N2000 (24 or 48 ports, with or without POE+) there is also the N3024F which offers 24 x SFP 1G ports. Unlike the N2000 series the N3000 has 'combo-ports': All 'copper' based switches offer 2 SFP 1Gb fiber ports (to be used instead of the two higherst numbered RJ45 1GBaseT port) and the N3024F offers two 1 GbaseT RJ45 combo ports (interface 23 and 24). All N3000 series switches also offer two SFP+ 10Gb uplink ports. Optionally
</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.