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

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

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

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

Document:
If a material change affects agreement, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent liability language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of termination, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent notice language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The administrator may rely on remedy 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 schedule threshold, and any dependency that could change the outcome. The procedure requires a comparison of exhibit, historical performance, and current constraints before the final recommendation is submitted. The compliance officer may rely on notice data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent warranty language, missing approvals, unusual timing, and obligations that.

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 member, historical performance, and current constraints before the final recommendation is submitted. The service owner may rely on network data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The review committee may rely on clinical data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent member language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 2.6 states that the operations lead must review appeal evidence before the submission date and document the rationale in the official record. Section 8.6 states that the service owner must review therapy evidence before the renewal date and document the rationale in the official record. The procedure requires a comparison of provider, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable screening threshold, and any dependency that could change the outcome. The service owner may rely on diagnosis.

Task: Extract all dates and deadlines.

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


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

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

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

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

Document:
Records should identify the decision maker, affected business unit, applicable portfolio threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable currency 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. A reviewer should flag inconsistent dividend language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 6.7 states that the operations lead must review asset evidence before the reporting date and document the rationale in the official record. Section 14.1 states that the service owner must review expense evidence before the reporting date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable margin threshold, and any dependency that could change the outcome. Section 1.9 states that the operations lead must review liability evidence before the escalation date and document the rationale in the official record. A reviewer should flag inconsistent currency language, missing.

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 worker data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The compliance officer may rely on latency data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent namespace language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent callback language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The procedure requires a comparison of cache, historical performance, and current constraints before the final recommendation is submitted. Section 7.5 states that the contract manager must review cache evidence before the renewal date and document the rationale in the official record. Section 13.6 states that the compliance officer must review migration evidence before the renewal date and document the rationale in the official record. The procedure requires a comparison of worker, historical performance, and current constraints before the final recommendation is submitted. If a material change affects endpoint, the service.

Task: Extract all monetary amounts.


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

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

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

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

Document:
The procedure requires a comparison of audit, historical performance, and current constraints before the final recommendation is submitted. Section 1.3 states that the review committee must review approval evidence before the renewal date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable monitoring threshold, and any dependency that could change the outcome. The procedure requires a comparison of approval, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable exception threshold, and any dependency that could change the outcome. Section 2.8 states that the contract manager must review attestation evidence before the submission date and document the rationale in the official record. Section 14.3 states that the service owner must review approval evidence before the certification date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable approval threshold, and any dependency that could change the outcome. The procedure requires a comparison of audit, historical performance, and current.

Task: Extract termination clauses.


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

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

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

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

Document:
Records should identify the decision maker, affected business unit, applicable analysis threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent sample language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects finding, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of analysis, historical performance, and current constraints before the final recommendation is submitted. The procedure requires a comparison of dataset, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable sample threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable model threshold, and any dependency that could change the outcome. If a material change affects variance, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 3.9 states that the compliance officer must review hypothesis evidence before the certification date and document the.

Task: Extract jurisdiction-specific requirements.


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

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

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

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

Document:
A reviewer should flag inconsistent notice language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The contract manager may rely on indemnity data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of termination, historical performance, and current constraints before the final recommendation is submitted. The contract manager may rely on warranty data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent confidential language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects schedule, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 15.4 states that the compliance officer must review confidential evidence before the implementation date and document the rationale in the official record. If a material change affects confidential, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The operations lead may rely.

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

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:
If a material change affects liability, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable amortization threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent revenue language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable liability threshold, and any dependency that could change the outcome. The service owner may rely on guidance data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects currency, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent segment language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The administrator may rely on expense data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Records should identify the decision maker, affected.

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:
Section 18.2 states that the service owner must review cache evidence before the escalation date and document the rationale in the official record. If a material change affects migration, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects cache, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The service owner may rely on configuration data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent schema language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. The contract manager may rely on latency data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 17.7 states that the administrator must review cache evidence before the renewal date and document the rationale in the official record. Section 15.1 states that the review committee must review deployment evidence before the certification date and document the rationale in.

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:
Records should identify the decision maker, affected business unit, applicable incident threshold, and any dependency that could change the outcome. 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 access, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent classification language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable retention threshold, and any dependency that could change the outcome. If a material change affects risk, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 6.8 states that the operations lead must review monitoring evidence before the escalation date and document the rationale in the official record. A reviewer should flag inconsistent retention.

Task: Extract all entities.


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

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

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

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

Document:
If a material change affects metric, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable dataset threshold, and any dependency that could change the outcome. If a material change affects ablation, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 5.8 states that the contract manager must review experiment evidence before the submission date and document the rationale in the official record. If a material change affects appendix, the contract manager must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The compliance officer may rely on metric data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects metric, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects analysis, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit.

Task: Extract all monetary amounts.


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

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

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

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

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

Task: Extract termination clauses.