entity-extraction

Extract domain-specific entities from documents using regex and LLM methods.

13|4|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/memect/kc --skill entity-extraction-memect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: entity-extraction
Source: https://github.com/memect/kc/tree/main/template/skills/zh/entity-extraction
Command: npx skills add https://github.com/memect/kc --skill entity-extraction-memect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract domain-specific entities from documents to support verification rules, enabling reliable extraction of numbers, dates, names, amounts, clauses, and other domain data after the relevant section has been located.

Core Features & Use Cases

  • Extraction method selection: choose between regex and LLM approaches, with guidance on schema design and postprocessing.
  • Structured outputs: define a schema that captures value, unit, raw_text, source_location, confidence, and extraction_method for auditable verification.
  • Workflow integration: design extraction steps to plug into worker LLM workflows or automated QC pipelines.

Quick Start

Extract a numeric amount and a date from the provided document using the defined extraction schema.

Frequently Asked Questions about entity-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract specific entities like amounts and dates from legal documents for compliance verification?

To extract entities for compliance verification, apply regex or LLM methods to target document sections, using a structured schema to capture values, source locations, and confidence scores for downstream rules.

What is the best way to choose between regex and LLM approaches for document entity extraction?

Choosing between regex and LLM approaches for entity extraction depends on your document structure: regex offers precise pattern matching for standardized formats, while LLM methods handle complex clauses and contextual data within a post-processing pipeline.

Can I integrate extracted document entities into an automated QC pipeline?

Yes, you can integrate extracted document entities into an automated QC pipeline by defining a structured output schema that captures value, raw text, and confidence annotations to feed downstream worker LLM workflows.

Do I need a predefined schema before extracting domain-specific data from text?

Yes, you need a design-ready schema before extracting domain-specific data from text, as it dictates how values, units, source locations, and confidence scores are structured for reliable downstream decision making.

How does confidence annotation work when extracting clauses for regulatory compliance?

Confidence annotation during regulatory clause extraction works by scoring the reliability of the extracted text against the defined schema, providing clear annotations that feed downstream verification rules and automated decision making.

What limitations exist when using regex for domain-specific entity extraction from unstructured text?

Regex for domain-specific entity extraction from unstructured text struggles with contextual ambiguity and complex phrasing, making it necessary to apply robust post-processing or optional LLM methods to achieve reliable verification outputs.