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>
History of trams in Leipzig Leipziger Verkehrsbetriebe GmbH (LVB, "Leipzig Transport Company, LLC" ) operates one of Germany's largest tramway networks. The tramway network history is presented below in tabular form, including opening, electrification, and closing dates by segment. Street names of the time are used in the tables, with current names in (parentheses). Network Development Leipziger Pferde-Eisenbahn-Gesellschaft (LPE, "Leipzig Horse Railway Company") On 20 April 1871, the Leipzig local authority granted to Count ("Graf") Gabriel Diodati and Geneva banker Adolph Schaeck a concession for construction of horse tramway lines. Construction was started in February 1872. On 24 May 1872, six days following the opening of the initial segment, the company, its property and concession was taken over by the Leipzig Tramways Company Ltd., organized in London by the British engineer Hutton Vignoles. The undertaking continued to use the LPE title in the German Empire. The LPE was taken over on 1 January 1896 by the Großen Leipziger Straßenbahn (GLSt, "Greater Leipzig Tramway") undertaking. The First Phase of Construction (1872/73) The Second Phase of Construction (1881–1891) After the new transport system had worked satisfactorily and enjoyed increasing popularity with Leipzig citizens, the company planned extensions to link surrounding districts of Leipzig with the tramway network. Leipziger Elektrische Straßenbahn (LESt, "Leipzig Electric Tramway Company") The second tramway undertaking in Leipzig, the LESt, was founded on 3 April 1893 and entered into the municipal Trade Register (Handelsregister) on 7 May 1895. The electrical-equipment manufacturer AEG served as the principal financial backer of the new undertaking. Because LESt cars were painted red, the company was known colloquially as the Rote ("Red One"). The competing tramway enterprise (LPE, from 1896 the GLSt) operated blue cars, and was known as the Blaue ("Blue One"). The concession for construction and operation of electric tramways was granted to LESt on 28 February 1895. Construction began after a short planning period on 11 June 1895. Because of the regulation limiting the length of each LESt segment in the same road as competing lines to just 400 meters, the company built a substantial length of lines in parallel roads and unreasonable workings in nearby side streets, which remain today Development of the Concession Network (1896–1898) Short Extensions (1899–1917) After the backbone network of the LESt was developed, the company built only shorter extensions at various extremities and the town center. Issues related to the struggle between competing tramway enterprises proved burdensome to the local authority, and so merger of the companies was sought during the First World War. This was accomplished from 1 January 1917, when the LESt was absorbed by its larger competitor, the GLSt. Große Leipziger Straßenbahn (GLSt, "Greater Leipzig Tramway Company") The course of events prompted the LPE to convert its network to electric traction. For this purpose, on 15 November 1895 the Große Leipziger Straßenbahn AG was entered into the municipal Trade Register. Effective 1 January 1896, the LPE, together with its contracts with the electrical manufacturer Union-Elektricitäts-Gesellschaft (UEG) and the banking house of Becker & Co, was handed to GLSt. Electrification (1896–1897) Because the competing enterprise was already busy with construction of an extensive electric tramway network, electrification of the horse tramway lines had to be advanced hastily. Within 18 months, the entire horse traction network had been changed to overhead electric traction. Extensive Development of the Network (1897–1902) The company also built new lines, because many districts were not yet served by the Leipzig tramway network. The End of Network Expansion (1908–1917) After the GLSt completed its planned network, it began to build terminal loops at important terminals where space was available (Bahnhof
</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.