- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
CAST generates text candidates through shared semantic plans and narrative roles, then assembles synthetic tables using conditional reference matching, fixed-discriminator feedback, and reliability control while keeping the generative LLM frozen. Experiments across three datasets, multiple generators, and downstream modeling strategies report consistent utility improvements, with fixed-pool comparisons providing further evidence for the selection strategy.
Critical strengths
- Combining condition-compatible candidate construction with table-level selection offers a practical approach to text-rich tabular synthesis without generator fine-tuning.
- Improvements across tasks and fixed-pool comparisons provide convincing evidence that selection offers benefits beyond simply strengthening target-label cues.
Critical weaknesses
- SSG relies on prompts to preserve shared content, while validity checks do not directly detect evidence distortion or cross-field semantic contradictions, so utility gains do not sufficiently establish record-level semantic fidelity.
- Direct association-fidelity evaluation covers only sufficiently populated Cloth condition groups and uses the same types of predictive features as selection, leaving rare combinations and broader cross-field relationships insufficiently assessed.
Questions for authors
- When synthetic and reference records have different auxiliary-attribute labels, how does the predicted-class agreement term in Equation (6) avoid encouraging text inconsistent with the synthetic structured attributes?
- When an attribute’s sole valid predictor barely exceeds its baseline, Equation (4) still assigns it the full feedback budget, so how does RCS prevent weak proxies from disproportionately influencing selection?
- Does Table 11’s 102-minute runtime include retrieval, planning, four-candidate generation, and selection, and is its end-to-end scope comparable to AFT-Tab’s reported 157-minute training overhead?
5 comments
Official reply to Reviewer yuLS [2/2]
Q2. Budget allocation in Eq. (4).
Ans: RCS excludes weak proxies through gating, while the fixed budget W_a preserves weak but genuine associations in the objective. Scaling the budget by reliability yields no gain beyond seed-to-seed variation. To test this, we compared three budget rules on Cloth with the candidate pool fixed. Table R9 reports the utility of the default rule and the change under each alternative.
| Budget rule | Utility (Cloth) |
|---|---|
| RCS (default): gating, then reweighting within a fixed W_a | 65.63 |
| W_a scaled by reliability | +0.17 |
| w/o RCS + final mixing: no gating, equal split (Table 27) | −0.55 |
Scaling the budget changes utility by +0.17, within the seed-to-seed standard deviation of Full CAST (0.41, Table 21), whereas removing RCS lowers utility in all three seeds (Table 22). It is therefore gating that excludes unreliable feedback.
Keeping W_a fixed is a deliberate choice. A budget that shrinks with reliability would push weakly associated attributes out of selection, whereas faithful synthesis should preserve such associations, in line with the association-fidelity criterion of AFT-Tab [1]. In our runs, the only attribute ever left with a single valid term was Wine price, whose reliability is well above the gating threshold. We have added Table R9 and the gating statistics to Appendix E.
Q3. Scope of the 102-minute GPU time.
Ans: Thank you for pointing out this ambiguity. The 102 minutes are the total GPU time of CAST's full pipeline on Wine Reviews, covering retrieval, semantic-plan extraction, four-role generation, feedback-predictor fitting, and selection. All methods in Table 11 follow the same four-GPU accounting.
Most of this time is spent on plan extraction and generation, and the LLM is never updated. AFT-Tab's 157 minutes cover its training alone, before any generation, so CAST's full pipeline requires less GPU time than AFT-Tab's training. We have revised the corresponding sentence in Appendix D.1 to state both scopes.
Reference
[1] Zhang Y, Yan L, Duan S, et al. AFT-Tab: Adversarial Fine-Tuning for Tabular Data Synthesis with Long Text Columns. ACL 2026: 4581–4594.
Follow-up on our response
Dear Reviewer yuLS,
Thank you again for your positive assessment and your precise questions. We understand that this is a busy period, and we truly appreciate your time.
As the discussion period will close soon, we would like to gently check whether our responses have addressed your questions. In particular, Tables R6 and R7 address record-level fidelity and the coverage of the association evaluation, and Tables R8 and R9 analyze Equations (6) and (4).
If anything remains unclear, we would be glad to clarify it.
Best regards,
The Authors
Official reply to Reviewer yuLS [1/2]
We thank Reviewer yuLS for the positive assessment and the precise questions on Equations (4) and (6). We address each concern below.
Ans: A direct audit confirms record-level fidelity: synthetic text rarely contradicts its structured fields or reverses the evidence in its shared semantic plan.
Using Claude Opus 5.5 as the judge, we audited 1,254 real records and 1,253 synthetic rows, covering every candidate of each synthetic row (5,012 in total). The judge was blind to the narrative role, selection status, and method. It flagged two types of error: contradictions between text and structured fields, and reversals of the plan's evidence. Table R6 reports the rates.
Both errors are rare on all three datasets, and on Cloth and Wine synthetic text contradicts its structured fields less often than real text does. Synthetic text is therefore consistent with both its structured fields and the evidence from which it was written. We have added the audit protocol and results to Appendix D.4.
Ans: Beyond the populated Cloth groups, CAST is closer to the real data than AFT-Tab in every extended evaluation, and both evaluations are independent of selection.
We extended the evaluation to the sparse Cloth groups outside the main support, merged into one bucket, and to Wine and Kickstarter. We also added an association gap that covers every auxiliary attribute without group thresholds. It trains a model on synthetic text, tests it on real data, and compares it with a model trained on real text. Table R7 reports all results, with a split of the real data as the floor (lower is better).
AFT-Tab is slightly closer only on the populated Cloth groups, which is expected because its discriminator directly targets text–structure consistency [1]. On all other evaluations CAST is clearly closer, most notably on the sparse groups and on Kickstarter.
Both evaluations are independent of selection. The conditional-W1 evaluator (character n-grams, SVD, and ExtraTrees) is fit only on real data. The association gap uses the same model family, trained separately on real and synthetic text. Selection, by contrast, relies on word-level TF-IDF text predictors. We have added Table R7 to Appendix E and described the evaluators, support, and coverage in Appendix C.2.
Ans: We thank the reviewer for this careful reading of Eq. (6). The reviewer is correct that, for an attribute outside the condition key, the term can favor a text whose predicted class matches the reference rather than its own label. In practice, however, the term changes few selections. To quantify this, we removed the term for one attribute at a time and re-ran selection on the fixed pool. Table R8 reports the number of changed selections and how many of them occur where the candidate and reference labels differ.
On Cloth, the issue does not arise in practice. Division Name, the attribute with the most label mismatch, fails gating. For Department Name, the changes occur almost exclusively where the labels agree. In these rows, the term keeps the own-label accuracy of the selected text close to that of real records.
The issue does arise for ordinal attributes such as Wine points. Even there, it affects only a small fraction of selections, the term carries a small weight (β·W_a ≈ 0.12), and the expected-level residual already compares levels. We have documented this case in Appendix B.3.