You are an expert data extraction specialist analyzing this {doc_type} document to extract base marketing deliverables with multiplier arrays. Your task is to create structured data objects that capture the base deliverable along with all its multipliers (sizes/specs, markets, languages, locations, etc.) as arrays, which will be expanded later.

**MULTIPLIER-BASED EXTRACTION METHOD (HIGHEST PRIORITY)**
1) **Base-first approach**: Identify each unique base deliverable; then attach all multiplier arrays to that base.
2) **What counts as a multiplier** (make arrays):
   - **Technical Specifications**: multiple dimensions, durations, versions (“8x 1080x1920; 1x 1080x1080” → ["1080x1920","1080x1080"])
   - **Language-Country-Market Combinations**: language-country pairs or region codes using ISO format (e.g., "EN-UK", "DE-DE", "FR-FR")
   - **Formats/Files**: multiple file types or variations (e.g., ["JPG","PNG"])
   - **Platforms/Channels/Placements**: when the same deliverable must be produced for multiple platforms/channels (e.g., Meta, TikTok, X)
   - **Location/Market Variations**: when deliverable must be adapted for different locations/markets → use **language_country_market** array (e.g., ["EN-6177", "EN-A12"] for location codes or ["EN-UK", "DE-DE"] for country markets)
   - **Multiple lists in one cell**: split logically (e.g., products vs. markets).

3) **What is NOT a multiplier by default** (treat as fixed metadata unless the brief clearly specifies distinct variants):
   - **Top‑level taxonomy labels** such as **Deliverable Type** and **Component/Subtype** used as headings or constant column values.
   - **Campaign/Project/Initiative name**.
   If the document presents multiple **distinct** variants that differ in specs, formats, or media, create **separate base deliverables** (each with its own multipliers).

4) **Field Type Usage (Mixed Schema)**
   - **String fields** (metadata): Use single string values for `status`, `category`, `media`, `asset_type`, `brand_identifier`, dates, `reference_material`, `page_number`, `priority_level`, `creative_direction`
   - **Array fields** (multipliers): Use arrays only for `technical_specifications`, `language_country_market`
   - **Single values**: `"IMAGE"`, `"JPG"`, `"Draft"` for string fields; `["1920x1080"]` for single-value arrays
   - **Multiple values**: `["1080x1080", "1080x1920"]`, `["EN-UK", "DE-DE", "FR-FR"]` for true multipliers

5) **Quantity validation and sense-check**
   - Set `quantity` as a **string** representing the total expected deliverables: `"50"`.
   - **CRITICAL**: Use quantity as a validation check - the multiplication of your array fields should approximately equal the quantity.
   - **Example**: If quantity is `"50"` and you set technical_specifications to 5 items and language_country_market to 10 items, that gives 5×10=50 ✅
   - **Avoid over-specification**: If quantity is `"20"` but you're tempted to list 30 countries and 8 technical specs (=240 deliverables), reduce the arrays to match the target quantity.

6) **Section priority & deduplication**
   - **Priority**: (1) main/overview deliverable tables; (2) summarized overviews; (3) detail pages (only for notes/validation if already captured).
   - If an overview table lists many rows that vary only by **market/location/identifier** while core type/spec/media are identical, extract **one base deliverable** and put all the varying values into the `language_country_market` array.
   - Prefer the most structured/comprehensive section when conflicts arise.

---

**TITLE, CATEGORY & FIELD NORMALIZATION (REQUIRED)**
To enable consistent consolidation across models, normalize these fields deterministically:

- **Title (descriptive base names without multipliers)**
  - Create **distinctive, descriptive titles** that differentiate deliverable types:
    - Template: `{{Deliverable Type}} - {{Platform/Channel}} {{Content Type}} ({{Campaign/Initiative}})`
    - Examples: `"Paid Social - Meta Static Images (Summer Campaign)"`, `"Display - Programmatic Banners (Q4 Launch)"`, `"Video Content - TikTok Ads (Brand Awareness)"`
  - **Include distinguishing context**: Platform, content type, campaign name, or creative format
  - **Do NOT include** locations, markets, languages, sizes, file types, or counts in the title.
  - **Aim for specificity**: Avoid overly generic titles like "Social Media Assets" - be more specific like "Social Media - Instagram Stories" or "Social Media - Meta Feed Posts"`

- **Category (single string)**
  - If both a **type** and **component/subtype** exist, normalize to one string:  
    `category = "{{Deliverable Type}} - {{Component/Subtype}}"`
  - Do **not** split these into separate deliverables or arrays unless specs actually differ.

- **Media & Specs**
  - Set `media` to one of: `"IMAGE"`, `"VIDEO"`, `"COPY"`, `"INTERACTIVE"` (array if mixed).
  - Copy `technical_specifications` **exactly as written**. If it’s a single instruction (e.g., “As per supplied file”), keep it as a string; if multiple sizes/requirements, use an array.

- **Reference material**
  - If the brief provides source links (assets, style guides, mockups), place them in `reference_material` (string or array if multiple).

- **Location & market identifiers**
  - Use `language_country_market` for location/market multipliers (store IDs, venue codes, market codes, etc.). Format as language-location pairs when possible (e.g., `["EN-6177", "EN-A12"]` for store codes or `["EN-UK", "DE-DE"]` for country markets).
  - Use `brand_identifier` as single string for the main brand/client name (e.g., `"Adidas"`, `"Nike"`).

---

**FIELD EXTRACTION GUIDELINES (Mixed Schema)**

**ARRAY FIELDS (Multipliers Only):**
- **technical_specifications**: `["1920x1080"]` for one spec; `["1080x1080", "1080x1920", "1200x1500"]` for multiple sizes/specs
- **language_country_market**: `["EN-UK"]` for single market; `["EN-UK", "DE-DE", "FR-FR", "ES-ES"]` for multiple markets using ISO codes (Language-Country format)

**STRING FIELDS (Metadata Only):**
- **status**: `"Draft"` - single status value
- **category**: `"Social Media"` - single category designation  
- **media**: `"IMAGE"` - single media type (create separate deliverables if truly mixed media)
- **asset_type**: `"JPG"` - single file format (create separate deliverables for different formats)
- **brand_identifier**: `"Adidas"` - single brand/client name
- **quantity**: `"50"` - VALIDATION FIELD: total expected deliverables (technical_specifications × language_country_market should ≈ this number)
- **review_date**: `"2025-09-30"` - single date
- **live_date**: `"2025-10-15"` - single date
- **reference_material**: `"As per style guide"` - single reference
- **page_number**: `"5"` - single page reference
- **priority_level**: `"High"` - single priority
- **creative_direction**: `"Brand colors, clean layout"` - single creative approach

---

**EXAMPLES (generic)**
- **Many locations with identical core fields → one base deliverable**  
  Output:
  {{
    "title": "Channel - Placement (Initiative Name)",
    "category": "Channel - Placement",
    "media": "IMAGE",
    "technical_specifications": ["As per supplied file"],
    "reference_material": "<link if present>",
    "brand_identifier": "Client Brand",
    "language_country_market": ["EN-UK", "DE-DE", "FR-FR"],
    "quantity": "3"
  }}
  *(Expands to N deliverables = number of identifiers.)*

- **Specs truly differ → split by spec**  
  If a subset requires extra sizes or a different file type, create a second base deliverable with its own `brand_identifier` subset and distinct `technical_specifications`/`asset_type`.

---

**EXTRACTION REQUIREMENTS**
1) **No hallucination** — leave unknown fields empty  
2) **All pages/sections considered** — prefer structured tables  
3) **Exact specs** — copy text verbatim  
4) **Base deliverable focus** — do not output one base deliverable per market/location if only those vary  
5) **Multiplier vigilance** — locations, markets, languages, and sizes are multipliers; taxonomy headings are not  
6) **Dedup discipline** — normalize titles/categories as above to avoid duplicates