By Anonymous User
Review Details
Reviewer has chosen to be Anonymous
Overall Impression: Weak
Content:
Technical Quality of the paper: Average
Originality of the paper: Yes, but limited
Adequacy of the bibliography: No
Presentation:
Adequacy of the abstract: Yes
Introduction: background and motivation: Limited
Organization of the paper: Needs improvement
Level of English: Satisfactory
Overall presentation: Weak
Detailed Comments:
Strengths
S1. Clinically meaningful focus on a PD monitoring/alerting ontology. (See C6)
S2. Useful comparative angle: four methodologies to test LLM-driven ontology creation.
S3. Interesting results and general analysis and domain
S4. Generally clear
Weaknesses
W1. Intro claims aren’t backed by LLM-relevant sources; “inadequate reasoning abilities” is unsupported. (See C1)
W2. Related work is thematically unfocused and incomplete (BERT vs LLMs, GPT vs ChatGPT, coverage stalls at 2023). (See C2)
W3. Methods lack specificity (one-shot/CoT not referenced; prompt sequence unclear; figure typo; RQs not set up in Intro). (See C3)
W4. Structure of the paper can be refined for clarity, broken down into multiple parts. (See C4)
W5. Reproducibility gaps: broken GitHub link and no code in the repo. (See C5)
Detailed comments
C1. Introduction (claims, sourcing, and clarity). The sources used to connect LLMs with ontological frameworks are not directly relevant to the paper’s claim; for instance, the second sentence cites a foundational ontology paper to support a trend about LLM-driven ontology construction, which doesn’t fit. Please replace with citations that fit the narrative. Also, “inadequate reasoning abilities” (line 21) needs grounding: inadequate relative to what, and with which source?
C2. Related work (scope, themes, and currency). This is the main weakness of the work. The literature review should be restructured by clearer themes. Right now it jumps from BERT-based ontology generation to LLM uses in other KE tasks (e.g., entity linking) without separation, and it does not discuss the important distinction between GPT (model) and ChatGPT (product/interface). Coverage effectively stops at 2023, yet there’s already an ESWC 2024 citation where multiple papers on ontology generation were published, and the area has since expanded. I recommend broadening the review via Google Scholar with filters from 2021 using terms such as “ontology generation” and “ontology learning,” following up related works, and incorporating representative examples (e.g., the first ones that appear with these filters: Lippolis et al., 2025; Qiu et al., 2024; Aggarwal et al., 2026; Elnagar et al., 2022). Many of these automate steps of existing OEMs and some are domain-specific (CS, life sciences, music, etc.), so they’re important to include. Also, because you use competency questions (CQs) in the methodology, briefly introduce what CQs are in Related Work before relying on them later.
C3. Research methodology (naming, sequencing, and figure). Please explicitly reference the one-shot and Chain-of-Thought methodologies you use. Provide a concise overview of the sequential prompts (what comes first, how you refine, and how CQs feed back), so the overall flow is unambiguous. The research questions appear in the figure but are not outlined in the Introduction: bring them forward so readers know what you’re answering before entering Methods.
C4. Experimental setup and evaluation could benefit from a separate section. Right now these details are embedded in Methods and are easy to miss. Please create a clearly labeled section that states who the human participants are, whether/which API is used, and other core setup details. Isolate the evaluation procedures there so readers can quickly understand how you assessed the hypotheses and methodologies. Limitations could also be a separate section from the conclusions.
C5. Reproducibility and artifacts. The GitHub link includes an extra trailing “t”, which breaks the URL. Remove it so the link opens correctly. Also, the repository appears to contain no code; please add the implementation if it is possible, along with usage guidelines, so the community can verify and reuse your approach.
C6. Overall contribution and domain fit. The approach and results are interesting, and the PD domain makes the work especially valuable. With a revision of all the areas of improvement identified, the paper’s practical impact will come through much more strongly.
Minor issues (typos & small fixes)
Line 16 (and onwards): quotation marks inverted.
Figure caption: “papers” → “paper’s”.
GitHub: remove the extra trailing t in the URL.
Line 25: “confirme” appears to be a typo (for "confirm")