Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
A reviewer should flag inconsistent dosage language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of coverage, historical performance, and current constraints before the final recommendation is submitted. Section 18.6 states that the administrator must review authorization evidence before the certification date and document the rationale in the official record. The contract manager may rely on network data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of member, historical performance, and current constraints before the final recommendation is submitted. If a material change affects coverage, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The contract manager may rely on diagnosis data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The service owner may rely on benefit data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 16.7 states that the.

Task: Extract jurisdiction-specific requirements.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
Records should identify the decision maker, affected business unit, applicable amortization threshold, and any dependency that could change the outcome. If a material change affects cashflow, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 1.2 states that the operations lead must review amortization evidence before the certification date and document the rationale in the official record. The procedure requires a comparison of forecast, historical performance, and current constraints before the final recommendation is submitted. If a material change affects cashflow, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent forecast language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent cashflow language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of dividend, historical performance, and current constraints before the final recommendation is submitted. The administrator may rely on cashflow data when the source is validated, the exception is.

Task: Extract exceptions and carve-outs.

All rows share the same extraction instruction, JSON schema, and few-shot prefix; only the short document and query change.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
Records should identify the decision maker, affected business unit, applicable endpoint threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent configuration language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable migration threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent callback language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent callback language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 3.1 states that the operations lead must review callback evidence before the renewal date and document the rationale in the official record. The review committee may rely on timeout data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent namespace language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of cache, historical performance, and current constraints before.

Task: Extract risks that require manual review.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
A reviewer should flag inconsistent retention language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of audit, historical performance, and current constraints before the final recommendation is submitted. Section 11.5 states that the service owner must review classification evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent incident language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of monitoring, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. Section 5.2 states that the service owner must review access evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent audit language, missing approvals, unusual timing, and obligations that conflict with the baseline.

Task: Extract all obligations.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
If a material change affects replication, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects cohort, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 9.6 states that the review committee must review finding evidence before the submission date and document the rationale in the official record. A reviewer should flag inconsistent replication language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The review committee may rely on cohort data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The operations lead may rely on hypothesis data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects hypothesis, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable metric threshold, and any dependency that could change the outcome..

Task: Extract all dates and deadlines.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
Section 1.1 states that the compliance officer must review exhibit evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent counterparty language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent schedule language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The service owner may rely on notice data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The administrator may rely on exhibit data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 16.4 states that the review committee must review termination evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable counterparty threshold, and any dependency that could change the outcome. The contract manager may rely on termination data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If.

Task: Extract all entities.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
If a material change affects coverage, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable dosage threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable benefit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent referral language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent exclusion language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of diagnosis, historical performance, and current constraints before the final recommendation is submitted. If a material change affects authorization, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of coverage, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent exclusion language, missing approvals, unusual timing, and obligations that conflict with the baseline policy..

Task: Extract all monetary amounts.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
If a material change affects portfolio, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The contract manager may rely on portfolio data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The administrator may rely on impairment data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 16.6 states that the contract manager must review margin evidence before the implementation date and document the rationale in the official record. The service owner may rely on quarter data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent revenue language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable currency threshold, and any dependency that could change the outcome. The operations lead may rely on margin data when the source is validated, the exception is approved, and the responsible owner confirms.

Task: Extract termination clauses.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
Records should identify the decision maker, affected business unit, applicable runtime threshold, and any dependency that could change the outcome. The procedure requires a comparison of endpoint, historical performance, and current constraints before the final recommendation is submitted. The compliance officer may rely on permission data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent deployment language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects permission, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects schema, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 13.3 states that the review committee must review latency evidence before the implementation date and document the rationale in the official record. The operations lead may rely on throughput data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag.

Task: Extract jurisdiction-specific requirements.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
Section 13.5 states that the review committee must review retention evidence before the submission date and document the rationale in the official record. Section 4.1 states that the operations lead must review policy evidence before the certification date and document the rationale in the official record. If a material change affects classification, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent policy language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent monitoring language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The contract manager may rely on attestation data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Records should identify the decision maker, affected business unit, applicable classification threshold, and any dependency that could change the outcome. Records should identify the decision maker,.

Task: Extract exceptions and carve-outs.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
If a material change affects cohort, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The operations lead may rely on observation data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The compliance officer may rely on metric data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 3.1 states that the contract manager must review methodology evidence before the escalation date and document the rationale in the official record. A reviewer should flag inconsistent metric language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects appendix, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable appendix threshold, and any dependency that could change the outcome. The contract manager may rely on experiment data when the source is validated, the exception is approved, and the responsible owner confirms.

Task: Extract risks that require manual review.


Prompt:
Instruction:
You are a careful information extraction system.
Return only valid JSON. Do not include markdown, commentary, or speculative fields.
Preserve source wording for quoted evidence. Use null when a requested value is absent.
Prefer arrays for repeated facts and include a confidence value between 0 and 1.

JSON schema:
{
  "document_type": "string",
  "entities": [
    {
      "name": "string",
      "role": "string",
      "evidence": "string"
    }
  ],
  "dates": [
    {
      "date": "YYYY-MM-DD or string",
      "meaning": "string",
      "evidence": "string"
    }
  ],
  "obligations": [
    {
      "party": "string",
      "action": "string",
      "deadline": "string|null",
      "evidence": "string"
    }
  ],
  "amounts": [
    {
      "value": "string",
      "currency": "string|null",
      "context": "string",
      "evidence": "string"
    }
  ],
  "risks": [
    {
      "risk": "string",
      "severity": "low|medium|high",
      "evidence": "string"
    }
  ],
  "confidence": "number"
}

Few-shot examples:
Example 1 document: Vendor must provide quarterly uptime reports within ten business days after quarter end. Customer may terminate after two uncured material breaches.
Example 1 output: {"document_type":"service agreement","entities":[{"name":"Vendor","role":"service provider","evidence":"Vendor must provide quarterly uptime reports"}],"dates":[{"date":"ten business days after quarter end","meaning":"report deadline","evidence":"within ten business days after quarter end"}],"obligations":[{"party":"Vendor","action":"provide quarterly uptime reports","deadline":"ten business days after quarter end","evidence":"Vendor must provide quarterly uptime reports within ten business days after quarter end"}],"amounts":[],"risks":[{"risk":"termination after repeated uncured breaches","severity":"medium","evidence":"Customer may terminate after two uncured material breaches"}],"confidence":0.92}
Example 2 document: The policy excludes experimental therapy unless approved by the clinical review committee before treatment begins.
Example 2 output: {"document_type":"medical policy","entities":[{"name":"clinical review committee","role":"approver","evidence":"approved by the clinical review committee"}],"dates":[{"date":"before treatment begins","meaning":"approval timing","evidence":"unless approved by the clinical review committee before treatment begins"}],"obligations":[],"amounts":[],"risks":[{"risk":"experimental therapy excluded without prior approval","severity":"high","evidence":"policy excludes experimental therapy unless approved"}],"confidence":0.9}
Records should identify the decision maker, affected business unit, applicable evidence threshold, and any dependency that could change the outcome. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision.

Additional extraction policy:
A reviewer should flag inconsistent vendor language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. Section 7.2 states that the operations lead must review access evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable access threshold, and any dependency that could change the outcome. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects classification, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 17.6 states that the compliance officer must review approval evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 5.8 states that the contract manager must review exception evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable audit threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent approval language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable encryption threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent access language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects attestation, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of encryption, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of incident, historical performance, and current constraints before the final recommendation is submitted. If a material change affects monitoring, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects risk, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects review, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent audit.

Document:
The administrator may rely on confidential data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of termination, historical performance, and current constraints before the final recommendation is submitted. Section 14.3 states that the operations lead must review obligation evidence before the submission date and document the rationale in the official record. Section 16.1 states that the compliance officer must review jurisdiction evidence before the reporting date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable exhibit threshold, and any dependency that could change the outcome. Section 4.4 states that the contract manager must review counterparty evidence before the submission date and document the rationale in the official record. A reviewer should flag inconsistent liability language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable assignment threshold, and any dependency that could change the outcome. The compliance officer may rely on agreement.

Task: Extract all obligations.