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 core. N-series switches run DNOS6.x on a Linux kernel. Legacy Powerconnect switches Current portfolio Below is an overview of the current portfolio of Dell Networking switches, including active models under the PowerConnect name. For legacy switches that are no longer being sold please check the Dell PowerConnect page and for non-ethernet Force10 products check the Force10 product page. Dell PowerConnect (For older products, not longer in active portfolio, please see the Dell PowerConnect page) The current portfolio of Dell PowerConnect rack switches consists of the following series: Power connect 2800 series : web-managed(only) 10/100/1000 ethernet switches Power connect 3500 series : managed 10/100 Mb layer 2 switches Power connect 5500 series : managed 10/100/1000 Mb layer 2 switches (with limited layer3 options) Power connect 6200 series : managed multi-layer gigabit Ethernet switches Power connect 7000 series : managed multi-layer gigabit Ethernet switches Power connect 8100 series : managed multi-layer tengigabit Ethernet switches The PowerConnects 2800, 3500 and 5500 are based on Marvell Technology Group equipment while the PowerConnect 6200, 7000, 8100 and the blade-switches PCM6220, PCM6348 and PCM8024(-k) are powered by Broadcom PowerConnect 2800 The Dell Networking PCT2800 web-managed switches are entry-level Ethernet switches that only offer a web-based GUI management interface. There are 4 models offering between 8 and 48 ports per switch. The interfaces on the switches are all copper-based gigabit Ethernet-ports and the 24 and 48 ports switches offer 2 or 4 'combo' ports where the last 2 (resp. 4) ports can use either the RJ45/UTP 1000BaseT copper-interface or a fiber SFP transceiver for uplinks to a distribution or core switch. All switches offer standard features like VLAN's, link-aggregation, auto-negotiation for speed- and duplex setting. The MAC address-table can hold up to 8000 MAC addresses in its forwarding table and have a 2Mb packet-buffering capacity PowerConnect 3500 The PowerConnect 3500 series switches are Ethernet access-switches which comes in 4 models: the PCT3524 and PCT3548 with 24 resp 48 10/100Mb ethernet ports and the PCT3524P / PCT3548P with 24 or 48 10/100Mb with PoE option to power VOIP phones, Wifi Access-points or IP camera's. All models can be provided with a redundant power-supply for either pure redundant power or to provide full PoE power-budget for the 48 ports PoE switch. The technical specifications of the 'non PoE' and the 'PoE' models are the same in regards to switching capabilities and the main difference between the 24 and 48 port models is the total forwarding rate of the switch: 12,8Gbit/s for both 24 port models and 17,6 Gbit/s for the 48 port models. As with the PCT2800 models the MAC address table can hold up to 8000 MAC addresses. Apart from all standard layer2 switching capabilities as VLAN's, link aggregation (static and LACP, dot1x access-security and dynamic vlan assignment, the switches also offer some basic IP routing/layer 3 processing. All PCT3500 switches offer two gigabit ethernet (1000BaseT) ports for high-speed uplinks to distribution or core switches or for stacking of switches and two gigabit SFP ports for a 1Gbit/s fiber transceiver for uplinks to distribution/core layer. PowerConnect 5500 The PowerConnect 5500 series switches are gigabit ethernet access-switches, available in 4 models: either a 24 or 48 port gigabit ethernet switch or a 24/48 port gigabit ethernet switch with power-over-ethernet option. Regardless of the model the switches offer two HDMI ports for stacking and two SFP+ 10Gbit transceiver ports for 10Gb uplinks. The technical specifications of the 4 models are all the same, except for the number of ports and the PoE feature and the total switching capacity of 128 Gbit/s (24 port) or 176 Gbit/s (48 port) with
</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.