--- license: cc-by-nc-sa-4.0 task_categories: - tabular-classification - tabular-regression language: - en tags: - optimization - optimization-modeling - natural-language-optimization - evaluation - metrics - retrieval - grounding - schema-parsing - lp - milp size_categories: - 1K= 0.8 AND type_match >= 0.8`. - `strict_ready`: `schema_hit AND param_coverage >= 0.8 AND type_match >= 0.8`. - `n_expected_scalar`: structural count of expected scalar slots used for evaluation. It is a small integer count and does not include slot names, variable names, formulation text, or problem text. - `n_filled`: number of scalar slots filled by the evaluated method. - `param_coverage`: scalar-slot coverage metric. - `type_match`: scalar-slot type compatibility metric. - `exact5`: exact-value metric at 5% tolerance where comparable; null means no comparable exact-value denominator for that row. - `exact20`: exact-value metric at 20% tolerance where comparable; null means no comparable exact-value denominator for that row. - `key_overlap`: schema/key overlap metric. ### `method_summary` Aggregate metrics for the pre-patch and final patched method variants. Counts are integer counts; rates and means are floating-point metrics. ### `strict_readiness_summary` Small aggregate table for strict-readiness counts and rate changes. ### `patch_transitions` Transition counts comparing pre-patch and patched outcomes. ID lists from the source transition file are deliberately excluded. ### `patch_case_metrics` Redacted per-case patch metrics for the changed-query audit. This config excludes source sentences, native query IDs, extracted mention strings, affected slot names, and multiplier expression text. It keeps only opaque IDs, change-status categories, readiness booleans, and numerical before/after metrics. ### `optmath_external_validation` An external validation configuration introduced in **v1.1** containing 1,000 detailed query-level mathematical parameter extraction metrics based on the OptMath dataset (`shushulei/OptMATH-Train`). This acts as an out-of-domain generalization and robustness test beyond the core NLP4LP benchmark. To guarantee zero reconstruction risk and strict adherence to text-free metrics, it contains absolutely no plaintext, retrieved passages, model responses, exact parameter arrays, or raw problem descriptions. Fields: - `example_uid`: Stable project-local opaque identifier derived via HMAC from the native source ID; raw mappings are not published. - `evaluation_domain`: Constant string (`OptMATH`). - `raw_ast_recall`: Recall score computed directly over total abstract syntax tree constants. - `text_supported_recall`: Recall score evaluated specifically over text-supported numeric slots. - `derived_recall`: Recall score evaluated over slots requiring mathematical derivation. - `is_complete`: Boolean indicator representing whether the instance was completely and perfectly extracted. - `num_gold_ast`: Total count of abstract syntax tree numeric constants defined by the gold benchmark. - `num_matched_ast`: Total count of correctly matched AST constants by the model. - `num_gold_text_supported`: Count of expected text-supported constants. - `num_matched_text_supported`: Count of matched text-supported constants. - `num_gold_derived`: Count of expected derived constants. - `num_matched_derived`: Count of matched derived constants. - `num_extracted`: Total number of numeric values extracted by the model. - `num_unsupported`: Count of extracted numbers unsupported by the source text annotations. ### `per_query_grounding_diagnostics` *(new in v1.2)* Per-query outcomes for **all 13 evaluated schema-retrieval/grounding method variants** (4,303 rows = 331 queries × 13 methods), extending `per_query_metrics` (which covers the single frozen `tfidf` method) to the full method comparison used by `grounding_method_summary`. Fields mirror `per_query_metrics` (`schema_correct`, `ordinary_ready`, `strict_ready`, `param_coverage`, `type_match`, `exact5`, `exact20`, `key_overlap`) plus `predicted_example_uid`/`gold_example_uid` (opaque, HMAC-derived — equal to `example_uid` on schema hits, different on schema misses) and `false_ready`, a boolean flagging cases that pass the readiness thresholds while `schema_correct` is false. No source text or native IDs are included, consistent with the rest of the release. ### `grounding_method_summary` *(new in v1.2)* One row per evaluated method (13 rows): aggregate `schema_R1`, ready counts/rates, Wilson 95% confidence intervals on strict-readiness (`strict_wilson95_low`/`strict_wilson95_high`), `false_ready_count`, and coverage/type-match/exact-match means. This is the method-comparison counterpart to `method_summary` (which only tracks the two pre-patch/patched `tfidf` states). ### `false_ready_details` *(new in v1.2)* The 124 rows across all 13 methods where `false_ready` is true in `per_query_grounding_diagnostics` (readiness thresholds passed despite an incorrect schema), with an added `gold_scalar_count` and a `taxonomy` label (`fewer_or_easier_scalar_slots` or `structurally_similar_schema`) categorizing why the false positive occurred. No mention strings, slot names, or source text are included — only opaque IDs, counts, and category labels. ### `bottleneck_taxonomy` *(new in v1.2)* 77 rows (13 methods × up to 6 buckets) counting failure-mode categories per method: `schema_wrong`, `schema_correct_coverage_failure`, `schema_correct_typematch_failure`, `schema_correct_both_coverage_and_typematch_failure`, `schema_correct_ready_but_exact20_not_full`, `schema_correct_ready_and_exact20_full`. Complements `grounding_method_summary` by breaking each method's failure count down by cause. ### `threshold_sensitivity` *(new in v1.2)* 27 rows sweeping `coverage_threshold`/`type_match_threshold` over `{0.8, 0.9, 1.0}` (a 3×3 grid) for the top 3 methods, reporting `ordinary_ready_count`/`strict_ready_count`/`false_ready_count` at each threshold pair. Shows how sensitive the readiness definition is to the two threshold choices used elsewhere in this release (0.8/0.8). ### `oracle_decomposition` *(new in v1.2)* A single-row decomposition of the gap between a retrieval oracle ceiling (`retrieval_ceiling_schema_R1=1.0`, i.e. perfect schema retrieval) and the achieved strict-ready counts for the baseline (`tfidf_typed_greedy`) and selective (`tfidf_selective_grounding_rerank`) methods, isolating how much of the remaining gap is attributable to retrieval error versus downstream grounding. ### `baseline_vs_selective_transition_details` *(new in v1.2)* Per-example transition records (12 rows, opaque `example_uid`/`gold_example_uid` only) for the queries where the baseline (`tfidf_typed_greedy`) and selective-rerank (`tfidf_selective_grounding_rerank`) methods disagree on `strict_ready`, `ordinary_ready`, or `schema_correct` — the discordant pairs underlying the McNemar tests in `baseline_vs_selective_transitions`. ### `baseline_vs_selective_transitions` *(new in v1.2)* Paired McNemar significance tests (3 rows, one per metric: `strict_ready`, `ordinary_ready`, `schema_correct`) comparing `tfidf_typed_greedy` against `tfidf_selective_grounding_rerank`, with discordant-pair counts, exact two-sided binomial p-values, and opaque discordant-example UID lists. `mcnemar_note` flags metrics with fewer than 10 discordant pairs as small-sample indications only. ### `historical_compatibility` *(new in v1.2)* Four rows recording pre-v1-pipeline historical readiness numbers for four methods, retained for internal compatibility bookkeeping only. Every row's `note` field explicitly warns these are a distinct, older measurement era and **must not be mixed or compared with** the fresh, canonical 257/331 and 331-query metrics reported elsewhere in this dataset. `source` intentionally does not name any internal file path or project directory — it identifies only that the numbers come from a historical, pre-release internal archive. ### `exact_metric_relationship` *(new in v1.2)* 13 rows (one per method) clarifying how the `exact5`/`exact20` exact-value metrics relate to readiness counts — in particular, that `exact5`/`exact20` are only populated when `schema_hit` is true (schema-gated by construction), so they cannot be directly compared to the unconditional `ordinary_ready_count`/`strict_ready_count` columns without accounting for that gating. ## Current Canonical Results The final patched method has: - schema R@1: `0.909366` - ordinary instantiation-ready: `265 / 331 = 0.800604` - strict instantiation-ready: `255 / 331 = 0.770393` - strict-ready patch gain: `+8` - strict-ready losses: `0` These are point-in-time results for the frozen method state represented by the source repository at commit `6bb75a4c4bed02c458ac30b4af206a2802fce095`. ## Limitations This is a benchmark-specific metrics release over NLP4LP `orig` evaluation queries. It does not contain the source benchmark examples, so users cannot inspect or resolve individual examples from this dataset alone. Users needing problem text or gold structures must obtain NLP4LP from the canonical upstream source. The dataset includes remaining non-ready cases, schema retrieval failures, and type/coverage failures. Null `exact5` and `exact20` values indicate rows without a comparable exact-value denominator, not successful or failed exact matching. The metrics are derived from one frozen pipeline/version. They should not be treated as claims about all natural-language optimization systems or all optimization-modeling benchmarks. ## Version History - **v1.2** (current): additive-only release. Adds 10 new configs (`per_query_grounding_diagnostics`, `grounding_method_summary`, `false_ready_details`, `bottleneck_taxonomy`, `threshold_sensitivity`, `oracle_decomposition`, `baseline_vs_selective_transition_details`, `baseline_vs_selective_transitions`, `historical_compatibility`, `exact_metric_relationship`) covering a 13-method schema-retrieval/grounding comparison, bringing the release from 6 configs / 1,377 rows to 16 configs / 5,954 rows. **No existing v1.1 config, column, or row was changed, renamed, or removed** — code reading any v1.1 config (`per_query_metrics`, `method_summary`, `strict_readiness_summary`, `patch_transitions`, `patch_case_metrics`, `optmath_external_validation`) continues to work unchanged. `size_categories` corrected from `n<1K` to the factually accurate `1K