This repository contains derived GGUF distribution artefacts for KGESH/nsfw-bge-m3-v5, a 1,024-dimensional BGE-M3 fine-tune. These files are quantisations and conversions of the original model; they are not independently trained models.

The source model is KGESH/nsfw-bge-m3-v5, evaluated at revision eaaf46c3b340d880d298ba7a03158fbe9b6e780b. No additional training was performed during conversion or quantisation. The F16 file is an unquantised GGUF conversion. Q8_0, Q6_K and Q5_K_M are lower-bit GGUF quantisations derived from that conversion. Please cite and follow the original model's licence, intended-use statement and limitations.

All files expose 1,024-dimensional embeddings in the tested llama-server configuration.

Send embedding requests to /v1/embeddings. The benchmark used the raw BGE-M3 serializer and cosine-compatible normalised embeddings; it did not use a Qwen instruction template.

The four candidates were evaluated as a paired, within-query multi-group experiment: the same 90-query retrieval fixture was run against F16, Q8_0, Q6_K and Q5_K_M. Each candidate was loaded in an isolated llama-server process, with an isolated SQLite store and no production retrieval path. The retrieval configuration was top-k 8, 30 lexical candidates, 30 dense candidates, and reciprocal-rank fusion k=60.

The supplied error-bar figure is shown below and is also available at figures/quantisation_metrics_with_95ci.png.

Error bars represent 95% confidence intervals: Wilson intervals for Recall@8 and paired bootstrap intervals for MRR@8 and end-to-end latency. The raw paired query results, summary statistics, group breakdowns, omnibus tests and post-hoc tests are provided alongside the figure.

The latency values above are end-to-end benchmark measurements and can vary with hardware, process state and server configuration. The exact machine-readable values are in quantisation_summary.csv.

The primary analysis used all four candidates together, rather than treating the comparison as a sequence of independent two-group tests. The significance threshold was alpha = 0.05.

The latency omnibus result indicates a statistically detectable difference in measured latency across candidates. It does not establish that one candidate is universally best, nor does it remove hardware and process-state confounding.

All six post-hoc candidate pairs were tested with paired methods and Holm correction within each metric. The complete results, including raw p-values, Holm-adjusted p-values and effect sizes, are in posthoc_tests.csv. Adjusted p-values for Recall@8 were 1.000000 for every pair. For MRR@8, no Holm-adjusted comparison was significant: the adjusted p-values were 1.000000, 1.000000, 1.000000, 0.652857, 1.000000 and 0.898562 in the file's pair order. For latency, all six Holm-adjusted comparisons were significant; the adjusted p-values ranged from 1.46e-15 to 5.31e-12.

On this 90-query fixture, all four candidates achieved the same Recall@8 (0.6667), and the omnibus MRR test was not significant. Q6_K was retained as a practical candidate for its size–quality trade-off, not because it was statistically superior to every other candidate. Q5_K_M had the lowest measured mean latency and smallest file, while Q6_K had the largest measured latency of the four in this run; these operational measurements should be repeated on the intended deployment hardware before selection.

The negative-query fixture returned a result for every negative query: negative_false_recall_rate = 1.0 and negative_no_result_precision = 0.0. This is a known evaluation limitation and must not be interpreted as reliable rejection, abstention or safety behaviour. The model is not a safety classifier, and users must apply appropriate access controls, content policies and human review.

The source data and training claims belong to the original model card. This derived repository does not make a new claim about the legality, completeness or representativeness of any source dataset. Review the original model's licence and intended-use restrictions before redistribution or deployment.

From the project workspace:

The analysis is paired and deterministic apart from server timing and the explicitly seeded bootstrap (20,000 resamples; seed 20260810). The benchmark code revision and source-model revision are recorded in analysis_metadata.json.

README.md is this model card. figures/quantisation_metrics_with_95ci.png is the error-bar figure. quantisation_summary.csv contains overall summary statistics; group_summary.csv contains per-query-group summaries; omnibus_tests.csv contains the four-group tests; posthoc_tests.csv contains all paired post-hoc tests with Holm correction; raw_query_results.json contains the paired observations; and analysis_metadata.json records provenance and analysis settings.