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>
MQX MQX RTOS is a real-time operating system developed by Precise Software Technologies Inc., and currently sold by Synopsys, Embedded Access Inc, and NXP Semiconductors. MQX is an abbreviation standing for Message Queue eXecutive. Like most real-time operating systems, MQX RTOS includes a multitasking kernel with pre-emptive scheduling and fast interrupt response, extensive inter-process communication and synchronization facilities, and a file system. Its configurable size conserves memory space taking as little as 6 KB of ROM, including its kernel, interrupts, semaphores, queues and a memory manager. MQX RTOS includes a TCP/IP stack (RTCS), embedded MS-DOS file system (MFS), USB Host/Device Stack, as well as Design, Task-Aware debugging (TAD), Remote debugging and performance analysis tools. It is supported by popular SSL/TLS libraries such as wolfSSL for increased security measures. MQX RTOS is generally used in embedded systems. MQX development is done on a "host" machine running Unix or Windows, cross-compiling target software to run on various "target" CPU architectures. MQX RTOS has been ported to a number of platforms and now runs on practically any modern CPU that is used in the embedded market. This includes Kinetis, ColdFire, PowerPC, ARC, ARM, StrongARM, xScale CPUs. All new Kinetis (ARM - CortexM4) and ColdFire devices are to be enabled with complimentary Freescale MQX RTOS. Freescale plans to expand the availability of this complimentary integrated enablement software to include many embedded processors in its broad portfolio. History MQX had its origins at Dy4 Systems Inc., a company based in Ottawa, Canada. A small team of software engineers at Dy4 consisting of Jeremy James, Mati Sauks and Craig Honegger started researching novel applications for embedded multiprocessors in 1984. This work led to the use of a real-time operating system in writing firmware for Dy4 single board computers. In 1989, Jeremy James and Mati Sauks commercialized the Harmony Real-time Operating System under the name of MPX, which was developed for portable multiprocessor real-time systems by the National Research Council Canada and created a company called Precise Software Technologies Inc. This effort led to the development of the Precise Real-Time Executive technology that was the basis of a product called MQX and MQX+m, which were real-time executives for single processor and multiprocessor applications. The unique asynchronous message passing paradigm delivered by MQX when it was introduced in 1991 and the royalty-free licensing model were accepted immediately in the embedded real-time market. Since the introduction of MQX, Precise continually added functionality to the MQX RTOS through it various iterations and versions. Precise Software Technologies Inc. was acquired by ARC International in March, 2000 and continued to develop, license and sell MQX on many new processor architectures including Freescale ColdFire, IBM/Freescale PowerPC and ARM. In 2004, Embedded Access assumed distribution and support of the MQX RTOS on non-ARC processor architectures. In 2009, Freescale began shipping the MQX RTOS complimentary with selected ColdFire MCUs. The MQX RTOS has been used in thousands of embedded projects by over 1000 companies, who have shipped millions of products running MQX. Today companies such as ABB, Agilent, ATI Technologies, Bausch and Lomb, General Dynamics, Daewoo, Exabyte, General Electric, B.F. Goodrich, Liebert, Matrox, Mitel Networks, Philips, Porsche, QLogic, SICK, Sony, Tyco and Xerox use MQX in applications such as Industrial Control, Networking, Storage and Consumer Electronics. References External links Freescale MQX RTOS Embedded Access Category:Real-time operating systems Category:Embedded operating systems Category:ARM operating systems Category:Microkernel-based operating systems Category:Microkernels
</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.