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 10.5 states that the service owner must review margin evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable revenue threshold, and any dependency that could change the outcome. Section 3.1 states that the service owner must review asset evidence before the escalation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable amortization threshold, and any dependency that could change the outcome. Section 17.5 states that the compliance officer must review portfolio evidence before the certification date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable impairment threshold, and any dependency that could change the outcome. If a material change affects portfolio, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent cashflow language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 18.2 states that the review.

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:
The operations lead may rely on configuration data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The compliance officer may rely on endpoint 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 cache, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 5.3 states that the contract manager must review serializer evidence before the submission date and document the rationale in the official record. The procedure requires a comparison of migration, historical performance, and current constraints before the final recommendation is submitted. Section 14.3 states that the service owner must review namespace evidence before the submission date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable runtime threshold, and any dependency that could change the outcome. Section 18.3 states.

Task: Extract all monetary amounts.

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:
The compliance officer may rely on access data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects access, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable exception threshold, and any dependency that could change the outcome. The review committee may rely on classification 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 policy threshold, and any dependency that could change the outcome. The procedure requires a comparison of retention, historical performance, and current constraints before the final recommendation is submitted. Section 11.1 states that the contract manager must review policy evidence before the implementation date and document the rationale in the official record. Section 12.4 states that the contract manager must review access evidence before the escalation date and document the rationale in the official record. Records should.

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:
A reviewer should flag inconsistent hypothesis language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 13.7 states that the contract manager must review analysis evidence before the submission date and document the rationale in the official record. The contract manager may rely on variance data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 3.9 states that the contract manager must review variance evidence before the implementation date and document the rationale in the official record. If a material change affects appendix, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects sample, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of replication, historical performance, and current constraints before the final recommendation is submitted. If a material change affects baseline, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change.

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:
If a material change affects counterparty, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable counterparty threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable counterparty threshold, and any dependency that could change the outcome. If a material change affects indemnity, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The service owner may rely on counterparty data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects agreement, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent exhibit language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent jurisdiction language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of assignment, historical.

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:
Records should identify the decision maker, affected business unit, applicable diagnosis threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable therapy threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent protocol language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 13.8 states that the administrator must review member evidence before the submission date and document the rationale in the official record. Section 10.7 states that the compliance officer must review appeal evidence before the renewal date and document the rationale in the official record. Section 4.5 states that the operations lead must review claims evidence before the implementation date and document the rationale in the official record. If a material change affects coverage, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 7.7 states that the operations lead must review benefit evidence before the submission date and document the rationale in the official record. A reviewer should flag.

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:
Records should identify the decision maker, affected business unit, applicable liability threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent guidance language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of segment, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent impairment language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects cashflow, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects forecast, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable guidance threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable quarter threshold, and any dependency that could change the outcome. If a material change affects quarter, the administrator must notify stakeholders, update the register, and preserve supporting artifacts.

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:
The service owner may rely on runtime data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of callback, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent configuration language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 9.1 states that the compliance officer must review schema evidence before the escalation date and document the rationale in the official record. The procedure requires a comparison of cache, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent runtime language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent permission language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of configuration, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable latency threshold, and any dependency that could change.

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:
The compliance officer may rely on access 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 access threshold, and any dependency that could change the outcome. Section 11.3 states that the review committee must review access evidence before the implementation date and document the rationale in the official record. A reviewer should flag inconsistent audit language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The contract manager may rely on access data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects approval, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 12.4 states that the compliance officer must review monitoring evidence before the renewal date and document the rationale in the official record. The procedure requires a comparison of review, historical performance, and current constraints before the final recommendation is submitted. Records should identify the.

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 observation, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent observation language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent appendix language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 8.4 states that the compliance officer must review observation evidence before the certification date and document the rationale in the official record. The procedure requires a comparison of appendix, historical performance, and current constraints before the final recommendation is submitted. The review committee may rely on hypothesis data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent metric language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 14.2 states that the administrator must review model evidence before the certification date and document the rationale in the official record. The operations lead may rely on observation data when the.

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:
The review committee may rely on agreement data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 11.7 states that the service owner must review jurisdiction evidence before the submission date and document the rationale in the official record. The procedure requires a comparison of termination, historical performance, and current constraints before the final recommendation is submitted. Section 3.4 states that the administrator must review agreement evidence before the renewal date and document the rationale in the official record. A reviewer should flag inconsistent indemnity language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent remedy language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The review committee may rely on breach 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 liability threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected.

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 therapy threshold, and any dependency that could change the outcome. The procedure requires a comparison of protocol, historical performance, and current constraints before the final recommendation is submitted. The administrator may rely on benefit data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects network, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of dosage, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent coverage language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The review committee may rely on appeal data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The service owner may rely on member data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 2.7 states that the service owner must.

Task: Extract jurisdiction-specific requirements.