GPE Framework - Greedy-Prune-Explain
GPE (Greedy-Prune-Explain) is a novel method for generating minimal, interpretable local explanations for decision tree predictions. Unlike existing methods like LIME, SHAP, or Anchors, GPE leverages the inherent structure of decision trees to produce explanations that are:
- ✅ Minimal — Contains only essential conditions (1-2 instead of 5)
- ✅ Precise — 99.4% precision on real-world financial data
- ✅ Fast — 48x faster than LIME, 19x faster than Anchors
- ✅ Actionable — Simple IF-THEN rules like "income < 50000 AND debt_ratio > 0.4"
📊 Benchmark Results
Tested on 3 financial datasets (632K records total):
| Method | Time (ms) | Complexity | Precision | Speedup |
|---|---|---|---|---|
| GPE-Core | 4.4 | 1.4 | 99.4% | 48x |
| GPE-IT | 3.0 | 1.4 | 97.9% | 71x |
| LIME | 213 | 5.0 | — | 1x |
| Anchors | 82 | 0.7 | 99.2% | 3x |
All results are statistically significant (p < 0.001)
🚀 Installation
pip install gpe-framework
Or install from source:
git clone https://github.com/vladdehtiarov/gpe-framework.git
cd gpe-framework
pip install -e .
📖 Quick Start
from sklearn.tree import DecisionTreeClassifier
from sklearn.datasets import load_iris
from gpe import GPEExplainer
# Load data and train model
iris = load_iris()
X, y = iris.data, iris.target
model = DecisionTreeClassifier(max_depth=5)
model.fit(X, y)
# Create explainer
explainer = GPEExplainer(
model=model,
feature_names=iris.feature_names,
X_train=X,
min_precision=0.95
)
# Explain a prediction
explanation = explainer.explain(X[0])
print(explanation)
Output:
============================================================
GPE Explanation (method: GPE)
============================================================
Prediction: 0
Rule: petal length (cm) <= 2.45
------------------------------------------------------------
Precision: 100.00%
Coverage: 33.33%
Complexity: 1 conditions
Reduction: 75.0% (4 → 1 conditions)
============================================================
Natural Language Output
print(explanation.to_natural_language())
The model predicts 'setosa' because petal length is at most 2.45.
This explanation covers 33.3% of similar cases with 100.0% accuracy.
🔧 GPE Variants
from gpe import (
GPEExplainer, # Standard (fast, greedy)
GPEInformationTheoretic, # Uses mutual information for pruning
GPECounterfactual, # Adds counterfactual explanations
GPEOptimal, # Exhaustive search for minimal rule
GPEEnsemble # For Random Forest, Gradient Boosting
)
# GPE-IT: Uses mutual information I(condition; prediction)
gpe_it = GPEInformationTheoretic(model, feature_names=features, X_train=X)
explanation = gpe_it.explain(x)
# GPE-CF: Includes counterfactual explanation
gpe_cf = GPECounterfactual(model, feature_names=features, X_train=X)
cf_explanation = gpe_cf.explain_with_counterfactual(x)
print(f"To change the decision: {cf_explanation.changes}")
GPE-Ensemble
GPEEnsemble explains Random Forest predictions with a consensus rule in three phases:
- Path Extraction — the decision path of
xin every tree, together with the tree's vote - Threshold Aggregation — for each feature, the bounds of the trees that voted for the ensemble's class are intersected into
[low_j, high_j]; a feature becomes a candidate when at leastM/2 + 1trees use it (aggregation='majority') or when the trees using it hold more than half of the total weight (aggregation='weighted', trees weighted by their accuracy on the training data) - Consensus Pruning — conditions are greedily removed while precision on the background set stays at or above
min_precision
from gpe import GPEEnsemble
explainer = GPEEnsemble(rf_model, feature_names=features, X_train=X_bg,
min_precision=0.95, aggregation='majority')
explanation = explainer.explain(x)
explanation.metadata # voting_trees, candidates, consensus, meets_threshold
RandomForest with 50 trees (max_depth=8), 50 test instances × 3 runs, 100 background samples
(experiments/run_ensemble_benchmark.py, v1.2.0, Apple M1 Pro):
| Dataset | Time (ms) | Complexity | Precision | Coverage |
|---|---|---|---|---|
| Credit Risk | 28.8 ± 2.8 | 1.8 | 0.982 | 0.223 |
| Credit Card Fraud | 30.8 ± 6.1 | 1.0 | 1.000 | 0.902 |
| Lending Club | 33.6 ± 9.0 | 1.0 | 1.000 | 0.885 |
📖 How It Works
GPE operates in three phases:
1. GREEDY Phase
Extract the full decision path from root to leaf:
Root → income <= 50000 → debt_ratio > 0.4 → ... → Leaf (denied)
2. PRUNE Phase
Iteratively remove conditions that don't affect precision:
while conditions > 1:
for condition in rule:
precision_without = calculate_precision(rule - condition)
if precision_without >= threshold:
remove(condition)
3. EXPLAIN Phase
Return the minimal rule with metrics:
- Precision — Accuracy for instances satisfying the rule
- Coverage — Proportion of dataset satisfying the rule
- Complexity — Number of conditions
📊 Metrics
from gpe import (
precision_score,
coverage_score,
complexity_score,
fidelity_score,
stability_score
)
# Evaluate explanation quality
precision = precision_score(explanation, model, X)
coverage = coverage_score(explanation, X)
complexity = complexity_score(explanation)
🔬 Scientific Novelty
- GPE-Core — First local explanation method specifically designed for decision trees
- GPE-IT — Novel use of mutual information I(condition; prediction) for condition selection
- Theoretical guarantees — Proven precision bounds and O(n·d) complexity
- Practical efficiency — 48x faster than LIME on real data
📁 Project Structure
gpe-framework/
├── gpe/
│ ├── __init__.py # Public API
│ ├── core.py # GPEExplainer
│ ├── novel_methods.py # GPE-IT, GPE-CF (scientific contribution)
│ ├── variants.py # GPEOptimal, GPEWeighted, GPEMonotonic, GPEEnsemble
│ ├── explanation.py # Data structures
│ ├── metrics.py # Evaluation metrics
│ ├── tree_utils.py # Tree utilities
│ └── visualization.py # Plotting functions
├── tests/ # Unit tests
├── experiments/ # Benchmark scripts
└── docs/ # Documentation
🤝 Contributing
Contributions are welcome! Please read our contributing guidelines and submit pull requests.
# Install development dependencies
pip install -e ".[dev]"
# Run tests
pytest tests/ -v
# Format code
black gpe/
📜 License
MIT License - see LICENSE file for details.
👤 Author
Vladyslav Dehtiarov
- Email: vvdehtiarov@gmail.com
- ORCID: 0000-0002-1578-8588
- Affiliation: Sumy State University, Ukraine
📚 Citation
If you use GPE in your research, please cite:
@article{dehtiarov2026gpe,
title={The Greedy-Prune-Explain Method for Fast Generation of Local Explanations from Decision Trees in Binary Classification Tasks},
author={Dehtiarov, Vladyslav and Borovyk, Valentyna},
journal={Nauka i tekhnika sohodni (Science and Technology Today)},
year={2026},
note={Accepted for publication}
}
@article{dehtiarov2026gpeensemble,
title={The GPE-Ensemble Algorithm: Extending Local Explainability to Ensemble Decision-Tree Models},
author={Dehtiarov, Vladyslav and Borovyk, Valentyna},
journal={Nauka i tekhnika sohodni (Science and Technology Today)},
year={2026}
}
🔗 Links
Metadata
Release files for gpe-framework 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gpe_framework-1.2.0.tar.gz | 45.4 kB | With provenance | Details for gpe_framework-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gpe_framework-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for gpe_framework-1.2.0-py3-none-any.whl |
Total release size: 90.1 kB
Release files / gpe_framework-1.2.0.tar.gz
| Download URL | gpe_framework-1.2.0.tar.gz |
|---|---|
| Size | 45.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a5737bd7e1b69db1eb07e89139da2fc54d305fab39e9487c2503237d51cf95c
|
|
BLAKE2b-256 checksum How to use checksums |
41921e57eec91d91c66ce00b4dc8139754a2e4c2e58a84f746626a96ff76c490
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / gpe_framework-1.2.0-py3-none-any.whl
| Download URL | gpe_framework-1.2.0-py3-none-any.whl |
|---|---|
| Size | 44.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3171c852fd019359b5f6760c42dea6770d5c722d5a0c6d36bdd87affab0a963e
|
|
BLAKE2b-256 checksum How to use checksums |
98f27b1656bb428acbb70550933c6b9a109d73e647a3259fbb72017792e58dd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for gpe-framework 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for gpe_framework-1.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.