- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2(+1)
- Soundness
- 3(+2)
Read review
Paper summary
LENS-AD uses a large language model (LLM) to construct derived features and overlapping prediction views from task descriptions and column metadata. A TabPFN or TabICL predictor is fitted to each view and to the full feature set using the available anomaly training labels. Semantic-Guided Meta-Aggregation (SGMA) learns from labeled source tasks how to predict view weights, then combines target predictions into an anomaly ranking without target validation labels. All splits and seeds of the target dataset are excluded from meta-training. Experiments cover all 20 ReTabAD task, six setings with few labeled anomalies or few training rows, and three seeds. The contribution is the integration of constrained feature construction, semantic prediction views, and transferred aggregation, with more consistent benefits when few anomalies are labeled.
Critical strengths
-
I appreciate the practical problem the paper addresses and the constraints placed on knowledge generation. Feature and view proposals use metadata without access to sample values or evaluation labels, and a fixed operator library controls how transformations are executed. This makes the resulting features inspectable and avoids choosing them through unreliable target validation feedback. The evaluated dataset is also excluded from meta-training across all splits and seeds. These are useful design choices for making domain knowledge usable when meaningful metadata is available and target supervision is scarce (Sections 3.2-3.4, Appendices C-D and E.1).
-
The reported results support the practical value of the complete workflow on metadata rich tasks. Table 4 reports mean area under the precision-recall curve (AUPR) of 0.616 across six settings, compared with 0.600 for the raw all-feature predictor and 0.602 for expansion alone. The expanded system also improves over raw semantic views using the same aggregation architecture by 0.018 and 0.019 at five and ten labeled anomalies. The parent feature controls and matched member stacking comparison add evidence that the integration is useful. ReTabAD is an appropriate metadata rich benchmark, and using all 20 tasks with two base predictors provides a reasonable evaluation of the stated setting (Tables 3-5, Appendices A.1, C.5, and E.5).
Critical weaknesses
-
As currently presented, the novelty appears incremental, and the specific methodological contribution needs a clearer explanation. SemanticMask (Tao et al., 2024) already uses column semantics and an optional task description to construct contrastive views, while existing LLM-based feature-engineering methods generate derived features. LENS-AD adds mechanism-oriented prediction members and transferred aggregation, but I would like a more precise account of what these additions contribute and why semantic organization should help under scarce supervision. A brief comparison of the semantic inputs, feature/view construction, and aggregation, linked to supporting results, would help establish the distinction. Table 4 supports the value of the complete framework beyond feature expansion alone, but leaves the specific contribution of semantic guidance less clearly separated from the broader benefits of subspace ensembles and learned aggregation (Sections 2-3 and Table 4).
-
I also found the method difficult to follow, particularly how generated features become prediction views and how the member predictions are combined into an anomaly score. Figure 2 conveys the overall stages, but the per-view predictors, label inputs, and distinction between source-side learning and target inference are not sufficiently clear. It aggregation equation should also be consistent with the scoring rule in the text. A worked example following one normal row and one anomalous row through the full pipeline would make these connections easier to understand. The method's reliance on meaningful column semantics and task metadata also needs a clearer discussion of applicability. The minimum metadata requirements, any fallback behavior, and the expected usefulness of semantic guidance when descriptions are missing, redacted, or unreliable should be stated explicitly (Figure 2, Sections 3.2-3.4, and Appendices A.1, D.2, and E.1-E.4).
Questions for authors
-
In my experience, many datasets do not always have clearly defined or meaningful semantic columns or metadata this is usable. This is especially prevalent in industries like finance and healthcare were datasets are intentionally opaque or redacted. How does this approach fare on cases like this? I do not see this in the paper anywhere, and it appears to be a significant limitation to this method. More specifically, what semantic metadata does the method minimally require, and what happens when column or metadate descriptions are missing, redacted, or unreliable? Please clarify any fallback behavior and the settings in which the semantic guidance is expected to be useful.
-
Additionally, it is unclear to me which elements or specific contributions of LENS-AD provide a significant methodological advance or novelty over prior work. SemanticMask, as mentioned in the related work section, already uses column semantics, and its task-aware variant incorporates a task description when constructing contrastive views. LLM-based feature engineering also seem quite similar in that they already generate derived features. What specifically does LENS-AD add to these approaches? A brief comparison of the semantic inputs, feature/view construction, and aggregation, linked to supporting results, would help. In particular, why should semantic organization help under scarce supervision, and what does Table 4 establish about its specific contribution relative to the broader benefits of subspace ensembles and learned aggregation?
-
Finally, as mentioned, found the method difficult to follow. It took several rereads and section cross referencing before I felt like I understood it. Could you walk through one normal row and one anomalous row from the original features to the final anomaly score? Please show how features are generated, assigned to subspaces, used by predictors fitted with the available anomaly labels, and ultimately combined. Figure 2 conveys the overall stages, but I still struggled to reconstruct the prediction procedure. Explicitly showing the per-view predictors and label inputs, separating source-side learning from target inference, and making the scoring equation consistent with the text would improve clarity.
8 comments
Response to Reviewer ga7a (2/3)
Q2.1. What are the specific methodological advances of LENS-AD over existing approaches, particularly SemanticMask and LLM-based feature engineering, in terms of semantic inputs, feature/view construction, and aggregation?
A2.1. Methodological novelty and comparison with prior work.
We thank the reviewer for this question. While prior work has explored column semantics and LLM-based feature engineering, LENS-AD addresses how to complement scarce target supervision with LLM knowledge, using it to guide feature expansion, mechanism-oriented prediction, and aggregation. The methodological differences are summarized below.
Table 2.1: Methodological comparison with related approaches.
| Method | Key Motivation | Semantic Inputs | LLM Sample Access | Feature / View Construction | Prediction Aggregation | Meta-learning |
|---|---|---|---|---|---|---|
| SemanticMask | Better contrastive views | Column & task semantics | No LLM | Semantic-aware masking | No aggregation | No |
| CAAFE | Better feature discovery | Column & task semantics | Sample values | Iterative feature generation | No aggregation | No |
| FeatLLM | Few-shot feature learning | Column & task semantics | Labeled examples | Rule generation + bagging | Ensemble averaging | No |
| LENS-AD (Ours) | Complementing scarce supervision with LLM knowledge | Column & task semantics | No samples | Feature expansion + mechanism grouping | Selective view weighting | Yes (view weighting) |
Unlike SemanticMask, which uses column semantics and task descriptions to construct masked views for self-supervised contrastive learning, LENS-AD uses LLM knowledge to derive new features and organize both original and generated features into mechanism-oriented prediction views. Each view serves as an independent anomaly predictor trained with scarce anomaly labels, with SGMA further learning how to aggregate their predictions across tasks.
Additional SemanticMask comparison. Although originally designed for one-class AD with clean normal data, SemanticMask was additionally evaluated under our few-shot protocol using the same splits. Disclosed anomalies were excluded from its unlabeled training pool, while undisclosed anomalies remained as contamination.
Table 2.2: Mean AUCPR over 20 datasets and six few-shot settings (three seeds; TabPFN backbone for LENS-AD).
| Method | Mean AUCPR (Rank) |
|---|---|
| CAD | 0.2573 (13) |
| WSAD-DT | 0.3468 (12) |
| SemanticMask | 0.3777 (11) |
| SemanticMask (task-aware) | 0.3843 (10) |
| PReNet | 0.4568 (9) |
| DevNet | 0.4607 (8) |
| FeatLLM | 0.4649 (7) |
| XGBoost | 0.4755 (6) |
| XGBOD | 0.5078 (5) |
| CAAFE | 0.5795 (4) |
| CatBoost | 0.5803 (3) |
| TabPFN | 0.6001 (2) |
| LENS-AD (Ours) | 0.6164 (1) |
LENS-AD achieves the highest mean AUCPR (0.6164), outperforming even the task-aware SemanticMask variant (0.3843) by 23.2 percentage points under the evaluated few-shot protocols.
Q2.2. Why semantic organization helps under scarce supervision.
A2.2. Under scarce supervision, anomaly detection faces two challenges:
- Difficulty in discovering anomaly mechanisms: With only a few labeled anomalies, it is difficult to reliably identify which feature combinations are informative for anomaly detection.
- Difficulty in selecting anomaly mechanisms: Different feature combinations may capture different aspects of anomalous behavior, but limited labels make it difficult to determine which mechanisms are more useful for identifying anomalies.
Importantly, the three components of LENS-AD are designed to work together rather than independently. Table 4 highlights this complementary effect: LKE alone yields only a modest gain (0.600 to 0.602), while applying SSD and SGMA directly to the raw feature space also brings limited improvement (0.600 to 0.605). In contrast, combining LKE with SSD and SGMA achieves 0.616. This suggests that LLM knowledge contributes not merely by expanding the feature space or organizing existing features, but through their combination: it enhances both what anomaly-relevant patterns can be captured and how they are modeled and integrated through complementary prediction views.
Together, these results support our central insight: LLM knowledge can be more effectively utilized under scarce supervision when it guides not only feature expansion, but also the organization and aggregation of prediction experts.
Response to Reviewer ga7a (3/3)
Q3. "Finally, as mentioned, found the method difficult to follow. It took several rereads and section cross referencing before I felt like I understood it. Could you walk through one normal row and one anomalous row from the original features to the final anomaly score? Please show how features are generated, assigned to subspaces, used by predictors fitted with the available anomaly labels, and ultimately combined. Figure 2 conveys the overall stages, but I still struggled to reconstruct the prediction procedure. Explicitly showing the per-view predictors and label inputs, separating source-side learning from target inference, and making the scoring equation consistent with the text would improve clarity."
A3. Clarification of the end-to-end prediction process. We thank the reviewer for this suggestion. We have redrawn Figure 2 to clarify the complete LENS-AD workflow and added Figure 3 to distinguish SGMA's source-side meta-training from target-side inference. We have also revised the method descriptions to improve clarity and consistency throughout the paper. Below, we walk through two real Automobile test samples under NLA=5 (seed 42): one normal and one anomalous.
(1) Dataset-level construction (LKE and SSD). Both stages use task descriptions and feature semantics, without accessing sample values or labels.
- LKE: The LLM uses domain knowledge to derive new concepts and relationships not explicitly represented in the original features. For example, the original
body-stylecolumn contains five categories (convertible, hardtop, hatchback, sedan, wagon). The LLM groups convertible and hardtop into a new sporty-body concept, creating a binary feature that indicates whether a car belongs to this group. It also derives a power-to-weight ratio from horsepower and curb-weight, since a car's acceleration capability depends on both engine power and vehicle mass. This creates a new, physically meaningful indicator of vehicle performance that may be relevant to insurance risk. These rules are compiled and applied to all rows, expanding 25 original features to 74 features (49 generated). - SSD: Using the task description and the semantics of all 74 features, the LLM proposes two candidate anomaly mechanisms: Luxury Make Risk and High-Performance Engine Risk. It assigns 16 and 53 relevant features to these two prediction views, respectively (e.g.,
sporty-bodyandpower-to-weightbelong to the Performance view). The remaining 5 features form an exploratory view, while a full-feature view using all 74 features serves as a fallback, yielding 4 prediction members in total.
(2) Instance-level scoring. Each of the four prediction members has an independent TabPFN predictor, fitted on the same 111 target training rows with only 5 revealed anomaly labels (all other rows are treated as negative). SGMA learns how to weight these predictors from the other 19 source datasets, without using target test labels. The resulting weights are shared by both test samples.
Table 3.1: End-to-end example on Automobile (NLA=5, seed 42).
| Normal Sample (row 28) | Anomaly Sample (row 131) | Aggregation Weight | |
|---|---|---|---|
| Original features | |||
| Make / body style | Honda / sedan | Toyota / convertible | |
| Horsepower / weight | 86 / 2304 | 116 / 2975 | |
| Generated features | |||
| Sporty-body indicator | 0 | 1 | |
| Power-to-weight | 0.0373 | 0.0390 | |
| View predictions | |||
| Luxury View | 0.0053 | 0.0793 | 0.263 |
| Performance View | 0.0065 | 0.3615 | 0.297 |
| Exploratory View | 0.0063 | 0.0966 | 0.135 |
| Full-feature View | 0.0023 | 0.3358 | 0.304 |
| Final anomaly score | 0.00445 | 0.21006 | |
| Anomaly rank (out of 48) | 42 | 1 |
The final score is computed by taking a weighted average of the view predictions in logit space, followed by a sigmoid transformation:
Here, is the prediction of the -th view, and is its SGMA weight. Higher scores indicate stronger evidence of an anomaly. In this example, the anomalous car receives a score of 0.21006 and ranks first among the 48 test samples, while the normal car scores 0.00445 and ranks 42nd.
This example illustrates the full process: LLM-generated features → mechanism-based views → independently fitted predictors → source-learned aggregation → final anomaly scores.
Response to Reviewer ga7a (1/3)
Q1. "How does the availability and quality of semantic metadata affect the performance of LENS-AD?"..."What semantic metadata does the method minimally require, and what happens when column or metadate descriptions are missing, redacted, or unreliable? clarify fallback behavior and the settings in which the semantic guidance is expected to be useful."
A1. Thank you for raising this important concern. We agree that the minimum semantic requirements and fallback behavior of LENS-AD should be better clarified. We therefore conducted additional experiments with different levels of metadata availability, progressively removing dataset descriptions, feature descriptions, and interpretable feature names across the LKE–SSD–SGMA pipeline. We organize the results into two analyses.
(1) How do dataset descriptions and feature descriptions affect performance?
We first examine the contributions of dataset descriptions and feature descriptions while retaining interpretable feature names.
Table 1.1 Effect of Dataset Descriptions and Feature Descriptions
The results indicate that dataset descriptions contributes more to performance than detailed feature descriptions.
(2) What happens when feature names are anonymized or all semantic information is removed?
We further examine the model's behavior when interpretable feature names are unavailable or when no semantic information can be provided.
Table 1.2 AUCPR of Dataset Descriptions and Feature Names (w/o Feature Descriptions)
As shown in Table 1.2, neither dataset descriptions nor feature names alone noticeably improve AUCPR (approximately 0.605), whereas providing both yields 0.610. This highlights a limitation of LENS-AD: effective semantic guidance requires both dataset context and interpretable feature information. When neither is available, LKE generates no additional features.
Overall, these results highlight two findings: (1) Curated feature descriptions are helpful but not essential; (2) LENS-AD relies on both dataset context and interpretable feature information to effectively leverage semantic knowledge. We will incorporate these findings into the revised ablation study and add a dedicated Limitations and Discussion section (Section 5).