Extraction procedure

Extraction procedure is one of Demiton's published registers for Australian civil construction. How a document type is parsed into structured facts. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.

Part of Platform in the register catalog.

Register ID

extraction_procedureUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A procedureA rule or method Demiton follows.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1 (1.0.3)Current version.

Download JSON SchemaSee an example record

Standards

This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.

• ISO 19650Information management using BIM - Part 2: Delivery phase of the assetsAustralia · 2019 · public summary
• ISO 19650Information management using building information modelling - Part 2: Delivery phase of the assetsInternational · 2018 · public summary

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

None planned yet.

Fields

10 fields: 3 required, 5 optional, 2 defined by each organisation.

Required

Every record carries these fields.

methodsList

The per-doc-type extraction methods; the payload the shelf exists to carry.

doc_typeText

Which document type this method configures.

Example: programme

org_entity_idWhole number

The org spine entity the current procedure is anchored to; makes the row per-org rather than per-tenant-blind.

Example: 501

Optional

Present when the source system records them.

statusText

Whether the operator has confirmed the procedure or it is still a candidate.

Example: completed

llm.modelText

The model chosen for the LLM extraction pass, e.g. a hosted chat model name.

Example: gpt-5.1

authored_byDateYYYY-MM-DD

Operator and timestamp recorded in _authored at write time.

parse.engineText

The primary text-lift engine, default pdfplumber

parse.ocr_fallbackTrue or false

Whether to OCR a page when the text-lift yields nothing.

Defined by each organisation

Their contents come from the organisation's own forms or systems, so they differ between organisations.

llm.promptText

The per-doc-type extraction system prompt.

parse.keyword_signalsList

Extra page-flag keywords added to the parser's built-ins.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

extraction_procedure.example.json

{
  "doc_type": "programme",
  "llm.model": "gpt-5.1",
  "methods": [
    "regex",
    "llm"
  ],
  "org_entity_id": 501,
  "source_system": "DEMITON",
  "status": "completed"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/extraction_procedure/v1.json

Show the full JSON Schema

Loading the schema…