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

Task: Extract all dates and deadlines.


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

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

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

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

Document:
A reviewer should flag inconsistent dividend language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable liquidity threshold, and any dependency that could change the outcome. Section 9.7 states that the service owner must review asset evidence before the certification date and document the rationale in the official record. A reviewer should flag inconsistent liability language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. A reviewer should flag inconsistent liability language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable segment threshold, and any dependency that could change the outcome. A reviewer should flag inconsistent asset language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Records should identify the decision maker, affected business unit, applicable currency threshold, and any dependency that could change the outcome. If a material change affects portfolio, the administrator must notify stakeholders, update the register, and preserve supporting.

Task: Extract all entities.

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


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

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

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

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

Document:
The review committee may rely on serializer data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. If a material change affects serializer, the compliance officer must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent configuration language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. If a material change affects deployment, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The operations lead may rely on permission data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 11.5 states that the review committee must review migration evidence before the submission date and document the rationale in the official record. A reviewer should flag inconsistent deployment 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. A reviewer should flag.

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:
A reviewer should flag inconsistent retention language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 14.3 states that the review committee must review vendor evidence before the reporting date and document the rationale in the official record. The procedure requires a comparison of approval, historical performance, and current constraints before the final recommendation is submitted. If a material change affects risk, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent encryption 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. If a material change affects review, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects control, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The procedure requires a comparison of access, 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 hypothesis threshold, and any dependency that could change the outcome. The administrator may rely on dataset data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The operations lead may rely on analysis 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 finding, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 4.7 states that the administrator must review sample evidence before the submission date and document the rationale in the official record. The contract manager may rely on dataset data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The contract manager may rely on dataset data when the source is validated, the exception is approved, and 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 obligation language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 13.5 states that the review committee must review indemnity evidence before the renewal date and document the rationale in the official record. The procedure requires a comparison of exhibit, historical performance, and current constraints before the final recommendation is submitted. Section 16.4 states that the contract manager must review agreement evidence before the certification date and document the rationale in the official record. Records should identify the decision maker, affected business unit, applicable warranty threshold, and any dependency that could change the outcome. If a material change affects remedy, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. If a material change affects governing, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The service owner may rely on remedy data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The administrator may rely on.

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:
The procedure requires a comparison of clinical, historical performance, and current constraints before the final recommendation is submitted. Section 6.6 states that the operations lead must review authorization evidence before the renewal date and document the rationale in the official record. The procedure requires a comparison of claims, historical performance, and current constraints before the final recommendation is submitted. Records should identify the decision maker, affected business unit, applicable protocol threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable dosage threshold, and any dependency that could change the outcome. If a material change affects protocol, the operations lead must notify stakeholders, update the register, and preserve supporting artifacts for audit review. The contract manager may rely on benefit data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. The procedure requires a comparison of therapy, historical performance, and current constraints before the final recommendation is submitted. The operations lead may rely on network data when the source is validated,.

Task: Extract risks that require manual review.


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

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

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

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

Document:
Section 5.4 states that the operations lead must review forecast evidence before the implementation date and document the rationale in the official record. The service owner 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 business unit, applicable impairment threshold, and any dependency that could change the outcome. Records should identify the decision maker, affected business unit, applicable liquidity threshold, and any dependency that could change the outcome. The administrator may rely on liquidity data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 6.7 states that the operations lead must review guidance evidence before the renewal date and document the rationale in the official record. The compliance officer 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 business unit, applicable portfolio threshold, and any dependency that could change the.

Task: Extract all obligations.


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

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

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

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

Document:
Records should identify the decision maker, affected business unit, applicable permission threshold, and any dependency that could change the outcome. The review committee may rely on permission data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. A reviewer should flag inconsistent permission language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 2.3 states that the compliance officer must review endpoint evidence before the reporting date and document the rationale in the official record. A reviewer should flag inconsistent cache language, missing approvals, unusual timing, and obligations that conflict with the baseline policy. Section 18.6 states that the service owner must review timeout evidence before the escalation date and document the rationale in the official record. If a material change affects endpoint, the administrator must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Records should identify the decision maker, affected business unit, applicable latency threshold, and any dependency that could change the outcome. The procedure requires a comparison of cache,.

Task: Extract all dates and deadlines.


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

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

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

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

Document:
The procedure requires a comparison of classification, historical performance, and current constraints before the final recommendation is submitted. Section 14.7 states that the compliance officer must review vendor evidence before the implementation date and document the rationale in the official record. If a material change affects control, the review committee must notify stakeholders, update the register, and preserve supporting artifacts for audit review. Section 1.1 states that the administrator must review monitoring evidence before the implementation date and document the rationale in the official record. If a material change affects evidence, the service owner must notify stakeholders, update the register, and preserve supporting artifacts for audit review. A reviewer should flag inconsistent exception 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. The procedure requires a comparison of vendor, historical performance, and current constraints before the final recommendation is submitted. A reviewer should flag inconsistent exception language, missing approvals, unusual timing, and.

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

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:
Records should identify the decision maker, affected business unit, applicable warranty threshold, and any dependency that could change the outcome. The procedure requires a comparison of liability, historical performance, and current constraints before the final recommendation is submitted. The review committee may rely on schedule data when the source is validated, the exception is approved, and the responsible owner confirms operational readiness. Section 8.5 states that the compliance officer must review remedy evidence before the renewal date and document the rationale in the official record. Section 9.3 states that the contract manager must review agreement evidence before the submission date and document the rationale in the official record. If a material change affects termination, 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 counterparty threshold, and any dependency that could change the outcome. Section 15.3 states that the review committee must review assignment evidence before the submission date and document the rationale in the official record. If a material.

Task: Extract termination clauses.