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>
L2 cache, or a higher-performance version (the R4000SC) with 1 MB of secondary cache in addition to the 16 kB of primary cache. As MIPS Computer Systems, Inc. had co-founded the Advanced Computing Environment consortium with Silicon Graphics, Microsoft, Motorola and others, the MIPS Magnum R4000 was intended to be MIPS' entry into the Windows NT workstation market. However, because MIPS Computer Systems, Inc.'s in-house effort to design a MIPS-based Windows NT system had met delays, MIPS Technologies abandoned its in-house efforts and instead licensed the Jazz design which Microsoft had developed in the early 1990s to facilitate the porting and development of Windows NT (it was first developed on the MIPS architecture, and was only later ported to the Intel 386, Alpha, and PowerPC architectures). As such, the MIPS Magnum R4000 (and indeed all Jazz-based systems, such as the Acer PICA, NEC RISCstation, Olivetti M700, etc.) incorporated many features more common to Intel-based PC's than to the commercial UNIX workstations of the era — for example, the Magnum R4000 included an EISA bus, used IBM PS/2-compatible keyboards and mice, and used commodity chipset components whose control registers were mapped to memory locations set forth in the IBM AT standard. Operating Systems The MIPS Magnum R4000 ran either Windows NT (beginning with version 3.1) when equipped with the little-endian ARC firmware, or RISC/os when MIPS Computer Systems, Inc.'s proprietary big-endian firmware (the "MIPS Monitor") was installed. The firmware could be switched between ARC or MIPS Monitor by loading either one into the Magnum's Flash memory/NVRAM from floppy disk, and thus the Magnum R4000 could dual-boot between Windows or Unix. Windows NT The MIPS Magnum R4000 was supported by Windows NT from version 3.1 (released in 1993) through version 4.0 (released in 1996). However, support by Microsoft for all MIPS systems ended after the release of Windows NT version 4.0, and useful software for Windows/MIPS — either from Microsoft or third-party vendors — was very scarce even when MIPS was supported (for example, Microsoft never ported its own Microsoft Office suite to MIPS). The MIPS Magnum 3000, unlike the MIPS Magnum R4000, was not able to run Windows NT. RISC/os All Magnums could run RISC/os, MIPS Computer System, Inc.'s proprietary port of UNIX. Running RISC/os on the MIPS Magnum R4000 requires use of the big-endian MIPS Monitor firmware. BSD The MIPS Magnum can run NetBSD, and it also ran OpenBSD at one point, but lack of developer interest and proper resources lead to the termination of the arch's support prior to the December 1, 1998 2.4 release. For the earlier, RISC/os-only MIPS Magnum 3000 machines, the correct port is NetBSD/mipsco. For the later, Windows NT-capable MIPS Magnum R4000, the correct port is NetBSD/arc. Linux The MIPS Magnum R4000 was among the earliest supported machines in the effort to port the Linux kernel to MIPS, with initial support begun April, 1995. Support for the Magnum R4000 became stable in the 2.1 development tree (around 1999); however, support for the Magnum in Linux has atrophied since then. QEMU The QEMU PC emulator version 0.9.1 can emulate the MIPS Magnum (and Acer Pica 61) using the "-M" parameter ("-M magnum" or "-M pica61"). QEMU can run the MIPS compiled version of Debian GNU/Linux on an x86 platform, along with Windows NT 3.5,3.51 & 4.0 with binaries here Offline publications BYTE, December 1990; Tom Yager. Sony NeWS and MIPS Magnum: A Double Shot of RISC External links Linux/MIPS article about Jazz architecture Information on MIPS systems NetBSD/mipsco port homepage NetBSD/arc port homepage Category:Computer workstations Category:Advanced RISC Computing Category:MIPS Technologies
</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.