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>
Y chromosome has been termed Azoospermia Factor (AZF) at Yq11 and subdivided into AZFa, AZFb, AZFc and possibly more subsections. Defects in this area can lead to oligospermia or azoospermia, however, a tight genotype-phenotype correlation has not been achieved. Spermatogenesis is defective with gene defects for the androgen receptor. Post-testicular azoospermia can be seen with certain point mutations in the cystic fibrosis transmembrane conductance regulator (CFTR) gene commonly associated with congenital vas deferens abnormalities. Genetic counselling is indicated for men with genetic causes of azoospermia. In terms of reproduction, it needs to be considered if the genetic defect could be transmitted to the offspring. BRD7 BRD7, a transcription regulatory protein, is normally highly expressed in the testis. Absent or reduced expression of BRD7 protein was observed in the testes of azoospermia patients exhibiting spermatogenesis arrest. Homozygous knockout mice [BRD7(-/-)] are infertile and have higher levels of apoptosis and DNA damage in their germline cells. Gene polymorphisms The human breast cancer susceptibility gene 2 (BRCA2) is employed in DNA repair. A common single nucleotide polymorphism in BRCA2 is associated with idiopathic male infertility with azoospermia. Four genes involved in DNA double-strand break repair and chromosome synapsis (TEX11, TEX15, MLH1 and MLH3) have key roles in genomic integrity, meiotic recombination and gametogenesis. Polymorphisms in these genes were tested for associations with male infertility. Single nucleotide polymorphisms in two of these genes (TEX11 and MLH3) were found to be associated with male infertility involving azoospermy or oligospermia. Diagnosis Azoospermia is usually detected in the course of an infertility investigation. It is established on the basis of two semen analysis evaluations done at separate occasions (when the seminal specimen after centrifugation shows no sperm under the microscope) and requires a further work-up. The investigation includes a history, a physical examination including a thorough evaluation of the scrotum and testes, laboratory tests, and possibly imaging. History includes the general health, sexual health, past fertility, libido, and sexual activity. Past exposure to a number of agents needs to be queried including medical agents like hormone/steroid therapy, antibiotics, 5-ASA inhibitors (sulfasalazine), alpha-blockers, 5 alpha-reductase inhibitors, chemotherapeutic agents, pesticides, recreational drugs (marijuana, excessive alcohol), and heat exposure of the testes. A history of surgical procedures of the genital system needs to be elicited. The family history needs to be assessed to look for genetic abnormalities. Congenital absence of the vas deferens may be detectable on physical examination and can be confirmed by a transrectal ultrasound (TRUS). If confirmed genetic testing for cystic fibrosis is in order. Transrectal ultrasound can also assess azoospermia caused by obstruction, or anomalies related to obstruction of the ejaculatory duct, such as abnormalities within the duct itself, a median cyst of the prostate (indicating a need for cyst aspiration), or an impairment of the seminal vesicles to become enlarged or emptied. Retrograde ejaculation is diagnosed by examining a post-ejaculatory urine for presence of sperm after making it alkaline and centrifuging it. Low levels of LH and FSH with low or normal testosterone levels are indicative of pretesticular problems, while high levels of gonadotropins indicate testicular problems. However, often this distinction is not clear and the differentiation between obstructive versus non-obstructive azoospermia may require a testicular biopsy. On the other hand, "In azoospermic men with a normal ejaculate volume, FSH serum level greater than two times the upper limit of the normal range is reliably diagnostic of dysfunctional spermatogenesis and, when found, a diagnostic testicular biopsy is usually unnecessary, although no consensus exists in this matter." But also, extremely high levels of FSH (>45 ID/mL) have been correlated with successful microdissection testicular sperm extraction. Serum
</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.