Skip to main content
Corpus-derived dictionaries often leave many words without POS tags — they were not in the seed data, are domain-specific, or are newly encountered. This module fills that gap by applying suffix patterns, prefix patterns, numeral detection, and an ambiguous-word registry to infer POS tags with confidence scores.

Overview

Purpose

During dictionary building, many words lack POS tags because:
  • They weren’t in the POS seed data
  • They’re domain-specific terms
  • They’re newly encountered words
The POSInferenceManager fills this gap using morphological rules.

POSInferenceManager Class

Applying POS Inference

Basic Usage

With Options

Parameters

Return Statistics

Statistics Fields

Inference Sources

The POSInferenceEngine uses multiple strategies:

1. Suffix Patterns

2. Prefix Patterns

3. Numeral Detection

4. Proper Noun Patterns

5. Ambiguous Words Registry

POS Coverage Statistics

Check POS tag coverage in the database:

Coverage Calculation

Database Schema

The manager updates these columns:

Column Usage

Integration with Pipeline

Best Practices

1. Run After Data Loading

The Pipeline.build_database() method handles this order automatically. For manual control, use POSInferenceManager directly after loading data via DatabasePackager.

2. Use Appropriate Thresholds

3. Check Coverage After Inference

See Also