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>
East Riding Amateur League The East Riding Amateur League was a football competition based in and around Kingston upon Hull, England. It had one division in its last season in the 2014-15 season, although in the past it has had as many as eight. Its top division nominally sat at level 13 of the English football league system and was a feeder to the Humber Premier League Division One. The league closed at the end of the 2014-15 season due to diminishing numbers. Most of its members joined the East Riding County League. Past champions (partial list) Premier Amateur/Senior Division 1991–92 Schultz Youth Club 1992–93 Reckitts 1993–94 Reckitts 1994–95 Reckitts 1995–96 Dairycoates 1996–97 Cottingham Sports Club 1997–98 Cottingham Sports Club 1998–99 Malet Lambert Youth Club 1999–2000 Hider Foods 2000–01 AutoMatrix 2001–02 East Hull Amateurs 2002–03 2003–04 2004–05 2005–06 AFC Wold 2006–07 Kinnersley 2007–08 Inter Charter 2008–09 Crown 2009–10 Pinefleet Wolfreton 2010–11 2011–12 Pinefleet Wolfreton 2012–13 Rapid Solicitors 2013–14 Dram Shop Premier Amateur Two/Division One 1991–92 Arthur Fish 1992–93 Cottingham Sports Club 1993–94 Youngs 1994–95 Kingburn 1995–96 East Hull Amateurs 1996–97 Fiveways 1997–98 Kevmar 1998–99 Tamerek Swiss Cottage 1999–2000 Nightjar 2000–01 Keyingham 2001–02 Fiveways 2002–03 2003–04 2004–05 2005–06 Eddie Beedle 2006–07 Hessle Sports Club Reserves 2007–08 AFC West Hull 2008–09 AFC Hull 2009–10 2010–11 2011–12 St Andrews reserves 2012–13 Eddie Beedle 2013–14 AFC Ramp Division Two 1991–92 Bulmans 1992–93 Techniflex 1993–94 North Ferriby United Reserves 1994–95 Fiveways 'A' 1995–96 Schooner Old Boys 'A' 1996–97 Merit Glazing 1997–98 Nightjar 1998–99 AFC Darleys 1999–2000 East Hull Amateurs reserves 2000–01 FC Kings Arm 2001–02 Northside Tigers 2002–03 Kinnersleys 2003–04 2004–05 2005–06 Crown 2006–07 Bridges 2007–08 AFC Preston Reserves 2008–09 Skippers AFC 2009–10 Queens County 2010–11 2011–12 Drum Athletic 2012–13 AFC Northfield Division Three 1991–92 Dentons 1992–93 Linley Haulage 'A' 1993–94 Fiveways 'A' 1994–95 Cogs 1995–96 Merit Glazing Rangers 1996–97 Paul Taylors 1997–98 AC Reckitts 1998–99 East Hull Amateurs Reserves 1999–2000 Keyingham 2000–01 Nightjar Reserves 2001–02 North Bransholme Community Association Division Four 1991–92 Eureka Club 1992–93 Springhead Old Boys 'A' 1993–94 Swallow 1994–95 Springhead Old Boys 'B' 1995–96 Skippers 1996–97 AC Reckitts 1997–98 Ideal Standard Reserves 1998–99 Tamerek Swiss Cottage Reserves 1999–2000 FC Wellington 2000–01 Hull Old Grammarians Reserves 2001–02 Wawne Mobiles Division Five 1991–92 Fiveways 'A' 1992–93 Hull Post Office 1993–94 Allclear Windows 1994–95 Smith & Nephew Reserves 1995–96 Kingburn Reserves 1996–97 Cumbrian Old Boys 'A' 1997–98 Bridges 1998–99 Kinloss 1999–0000 Hull Old Grammarians Veterans 2000–01 North Bransholme Community Association 2001–02 BP Interserve Division Six 1991–92 Springhead Old Boys 'A' 1992–93 Kirkways 1993–94 Sutton Fields SBCA 1994–95 Norths 1995–96 Nightjar 1996–97 Birdseye 1997–98 West Side 1998–99 Hull Old Grammarians Veterans 1999–2000 Britcom Trucks Division Seven 1991–92 Hull Post Office 1992–93 Foredyke 1993–94 Springhead OB 'C' 1994–95 Paul Taylor's 1995–96 Arion Transport 2nd Senior Cup 1991–92 Schultz 1992–93 Malet Lambert Youth Club 1993–94 Reckitts 1994–95 Cottingham Sports Club 1995–96 Dairycoates 1996–97 East Hull Amateurs 1997–98 Malet Lambert Youth Club 1998–99 East Hull Amateurs 1999–2000 Ideal Standard 2000–01 AutoMatrix 2001–02 Discount Carpets Intermediate Cup 1991–92 Cottingham Sports Club 1992–93 Eureka PDL 1993–94 Linley Haulage 1994–95 Wolfreton Youth Club 1995–96 Lord Nelson Rangers 1996–97 Merit Glazing 1997–98 Three Five Cars 1998–99 AC Reckitts 1999–2000 Everthorpe Sports 2000–01 Nightjar Reserves 2001–02 Northside Tigers Junior Cup 1991–92 Greatfield Old Boys 1992–93 Cavalier Wanderers 1993–94 Windsor Rangers 1994–95 Black Prince 1995–96 Nightjar 1996–97 FC Ridings 1997–98 West Side 1998–99 Kinloss 1999–2000 Hull Old Grammarians Veterans 2000–01 North Bransholme Community Association 2001–02 Kingston External links Official website Category:Football in the East Riding of Yorkshire Category:Defunct football leagues in England
</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.