voidx Strategy Bench

Loading results…

How accurate and how costly each extraction strategy is, measured against exact ground truth on seeded synthetic corpora and on real dumps. Recall and precision are over (subject class, property, object class or datatype) patterns. Estimates should have their 95 % bounds (±2·RSE before voidx 4b) hold the truth about 95 % of the time. An exact count that differs from truth at all is a defect.

Strategies at a glance

Cost against recall

HTTP requests sent (log scale), retries included, against the share of true patterns found. Up and to the left is better.

Estimate intervals holding the truth

Per strategy that produced estimates. The dashed line is the 95 % target.

Estimate error by quantity

Relative error of estimates against the non-blank truth: median and 95th percentile over each run's estimates, then the median over repetitions. Exact counts have no error: any difference is a defect.

Runs

Every repetition, with robustness counts from the outcomes voidx recorded. Select a run to see its patterns.

Patterns the run got wrong, missed, invented, estimated or only saw

Select a run above.

Queries the run sent

Select a run above.

Cost against accuracy, across tiers

One chart per mode, the baselines beside voidx's: each point is a (source, engine, faults) group's median HTTP requests (log scale) against its recall. voidx's points are coloured by tier; a baseline's take its mode's colour, with the tier as its outline. Every chart shares the same axes. Live endpoints have no truth, so they sit on a cost-only strip below, coloured by mode.