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>
MIPS Magnum The MIPS Magnum was a line of computer workstations designed by MIPS Computer Systems, Inc. and based on the MIPS series of RISC microprocessors. The first Magnum was released in March, 1990, and production of various models continued until 1993 when SGI bought MIPS Technologies. SGI cancelled the MIPS Magnum line to promote their own workstations including the entry-level SGI Indy. The early, R3000-based Magnum series ran only RISC/os, a variant of BSD Unix, but the subsequent Magnum workstations based on the Jazz architecture ran both RISC/os and Windows NT. In addition to these proprietary operating systems, both Linux and NetBSD have been ported to the Jazz-based MIPS Magnum machines. Some models of MIPS Magnum were rebadged and sold by Groupe Bull and Olivetti. In addition, headless (i.e., without a framebuffer or video card) versions were marketed as servers under the name "MIPS Millennium". Series Model number information. MIPS Magnum 3000 Alternative model name: MIPS RC3230 Release: March, 1990 Initial price: $9000 USD Bus: TURBOchannel Maximum possible RAM: 128 MB MIPS Magnum R4000 Two subtypes: The R4000 PC-50 and R4000 SC-50 Release: April, 1992 Initial price: $12,000.00 USD Bus: EISA Maximum possible RAM: 256 MB Components Processors The MIPS Magnum 3000 has a 25 or 33 MHz MIPS R3000A microprocessor. The MIPS Magnum R4000 PC-50 has a MIPS R4000PC processor with only 16 kB L1 cache (but no L2 cache), running at an external clock rate of 50 MHz (which was internally doubled in the microprocessor to 100 MHz). The MIPS Magnum R4000 SC-50 is identical to the Magnum R4000PC, but includes one megabyte of secondary cache in addition to the primary cache. Memory For main memory, the MIPS Magnum 3000 accepted 30-pin true-parity, 80ns SIMMs up to a maximum of 128 MB. The MIPS Magnum R4000 accepted eight 72-pin true-parity SIMMs, up to a maximum of 256 MB. SCSI The MIPS Magnum R4000 (both the R4000 PC-50 and R4000 SC-50) includes a single on-board SCSI bus using the on-board NCR 53c94 fast-narrow SCSI chipset. An internal cable with four 50-pin connections links internal SCSI devices, and also interfaces external SCSI devices via an endlink mounted on the rear of the case. Ethernet The MIPS Magnum R4000 includes an on-board SONIC Ethernet chipset and an AUI Ethernet connector mounted on the case. Framebuffer The video output for the Magnum R4000 consists of a proprietary framebuffer available as a custom full-length option card — the G364 framebuffer. The G364 includes a SUN 13W3-style output (which can be converted to the more common VGA pin-out), and is capable of pixel screen resolutions of 640x480, 800x600, 1024x768, or 1280x1024. Because it is a simple framebuffer, the G364 does not include any accelerated graphics functions. Serial and Parallel I/O The MIPS Magnum R4000 also includes two standard RS232-capable serial ports and an IBM AT-compatible parallel port. Floppy disk Also, the MIPS Magnum R4000 had an IBM AT-compatible floppy disk controller and a single floppy drive bay. Historical development The MIPS Magnum 3000 used a MIPS R3000 processor and a custom, proprietary motherboard which incorporated the TURBOchannel bus (it is noted that DEC also manufactured the DECstation line of workstations running Ultrix, which also used MIPS processors and the TURBOchannel bus). The Magnum 3000 ran only RISC/os, which was MIPS Computer Systems, Inc.'s proprietary port of BSD Unix including some System V features. The later Magnums, the MIPS Magnum R4000PC and MIPS Magnum R4000SC, also used a MIPS microprocessor — the MIPS R4000, a full 64-bit microprocessor available either in a low-cost version (the R4000PC) having 16 kB of L1 cache but no
</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.