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 amortization language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 12.3 states that the operations lead must review amortization evidence before the implementation date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable asset threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable expense threshold, and any dependency that could change the outcome. The administrator may rely on asset data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The contract manager may rely on portfolio data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of liquidity, historical performance, and current constraints before the final recommendation is submitted. If a material change affects liability, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 6.6 states that the operations lead.

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 callback threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable endpoint threshold, and any dependency that could change the outcome. Section 4.6 states that the review committee must review configuration evidence before the escalation date and document the rationale in the official record. The procedure requires a comparison of timeout, historical performance, and current constraints before the final recommendation is submitted. If a material change affects worker, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 11.7 states that the compliance officer must review configuration evidence before the submission date and document the rationale in the official record. The procedure requires a comparison of replica, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent deployment language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects endpoint, the operations lead must notify stakeholders, update the.

Task: Extract risks that require manual review.

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:
A reviewer should flag inconsistent evidence language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent incident language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent policy language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The compliance officer may rely on risk data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The operations lead may rely on monitoring data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of audit, historical performance, and current constraints before the final recommendation is submitted. The operations lead may rely on risk 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 vendor threshold, and any dependency that could change the outcome. If a material change affects encryption, the operations lead.

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:
Records should identify the decision maker, affected business unit, applicable hypothesis threshold, and any dependency that could change the outcome. The procedure requires a comparison of variance, historical performance, and current constraints before the final recommendation is submitted. The operations lead may rely on dataset data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The contract manager may rely on metric data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent replication language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects metric, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 3.2 states that the administrator must review metric evidence before the reporting date and document the rationale in the official record. The service owner may rely on experiment data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material.

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

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 contract manager may rely on claims data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent benefit language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects referral, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects appeal, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The review committee may rely on network data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent dosage language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 15.9 states that the administrator must review authorization evidence before the implementation date and document the rationale in the official record. A reviewer should flag inconsistent referral language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 17.8 states that the review committee.

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:
Section 14.6 states that the contract manager must review currency evidence before the submission date and document the rationale in the official record. The procedure requires a comparison of portfolio, historical performance, and current constraints before the final recommendation is submitted. If a material change affects impairment, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects impairment, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects cashflow, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects currency, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects revenue, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects portfolio, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The review committee.

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:
Section 4.2 states that the review committee must review schema evidence before the escalation date and document the rationale in the official record. The administrator may rely on migration 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 serializer threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent permission language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent throughput language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent replica language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable migration threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable callback threshold, and any dependency that could change the outcome. The procedure requires a comparison of deployment, historical performance, and current constraints before.

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:
A reviewer should flag inconsistent audit language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The review committee may rely on risk data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent policy language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of attestation, historical performance, and current constraints before the final recommendation is submitted. If a material change affects incident, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent policy language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of control, historical performance, and current constraints before the final recommendation is submitted. If a material change affects policy, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects approval, the administrator must notify stakeholders, update the register, and.

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:
Section 4.9 states that the service owner must review finding evidence before the submission date and document the rationale in the official record. A reviewer should flag inconsistent hypothesis language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent baseline language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects analysis, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The service owner may rely on sample data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent dataset language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 17.2 states that the compliance officer must review sample evidence before the implementation date and document the rationale in the official record. If a material change affects ablation, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects replication,.

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:
Section 1.4 states that the administrator must review warranty evidence before the certification date and document the rationale in the official record. Section 5.1 states that the compliance officer must review liability evidence before the renewal date and document the rationale in the official record. Section 18.7 states that the service owner must review warranty evidence before the renewal date and document the rationale in the official record. Section 15.7 states that the administrator must review governing evidence before the certification date and document the rationale in the official record. A reviewer should flag inconsistent schedule language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent governing 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. A reviewer should flag inconsistent exhibit language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable.

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 procedure requires a comparison of dosage, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable benefit threshold, and any dependency that could change the outcome. Section 11.8 states that the operations lead must review exclusion evidence before the escalation date and document the rationale in the official record. A reviewer should flag inconsistent member language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable therapy threshold, and any dependency that could change the outcome. The operations lead may rely on network data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The operations lead may rely on referral data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects coverage, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The contract manager may rely on authorization.

Task: Extract all dates and deadlines.