SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2407.19998 · 2024

Do LLMs Really Adapt to Domains? An Ontology Learning Perspective

arXiv · PDF · Open in the Atlas

Code that ran

3 of 7 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 0 honoured the contract we drafted, 0 violated it and 0 have no contract verdict; 3 failures of our instrument; 4 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2407.19998.json · badge: /api/ran/2407.19998.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
boschresearch/llm-vs-gibberish-ontologies canonical (classifier label)
classifier basis: census
3 ran · 4 no recorded run
FunctionStatusWhere it lives
get_referenced_concepts Ran
ran; our contract draft was wrong, not the code
boschresearch/llm-vs-gibberish-ontologies/wordnet-gibberish/extract.py
pointer only (licence: AGPL-3.0) · get_code("0be35ed4c2064631")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

parse_answer_json_2 Ran
ran; our contract draft was wrong, not the code
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/relation_extraction_gpt.py
pointer only (licence: AGPL-3.0) · get_code("f4564ff7c6a9fefb")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

shorten_uri Ran
ran; our contract draft was wrong, not the code
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/relation_extraction_gpt.py
pointer only (licence: AGPL-3.0) · get_code("2cd019ea569581f4")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

make_hypernym_datasets Not yet run
unverified (harvested, no recorded run)
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/finetune_ontology/datasets.py
pointer only (licence: AGPL-3.0) · get_code("f752395a120283e8")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded.

parse_answer_json Not yet run
unverified (harvested, no recorded run)
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/relation_extraction_gpt.py
pointer only (licence: AGPL-3.0) · get_code("79191d0c5c3bf96f")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded.

write_negative_prompt Not yet run
unverified (harvested, no recorded run)
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/finetune_ontology/datasets.py
pointer only (licence: AGPL-3.0) · get_code("551d94beed9aca79")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded.

write_prompt Not yet run
unverified (harvested, no recorded run)
boschresearch/llm-vs-gibberish-ontologies/finetune-llm-ontology/finetune_ontology/datasets.py
pointer only (licence: AGPL-3.0) · get_code("684d5a10a2176c99")
How it ran

The body of this sample is withheld: AGPL-3.0, as GitHub detects it on this paper's repository, boschresearch/llm-vs-gibberish-ontologies, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded.

Also present in other papers' code

Of 7 samples lifted from this paper's linked repositories, 7 carry a function identity and 0 do not. Of the 7 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 7 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Large Language Models (LLMs) have demonstrated unprecedented prowess across various natural language processing tasks in various application domains. Recent studies show that LLMs can be leveraged to perform lexical semantic tasks, such as Knowledge Base Completion (KBC) or Ontology Learning (OL). However, it has not effectively been verified whether their success is due to their ability to reason over unstructured or semi-structured data, or their effective learning of linguistic patterns and senses alone. This unresolved question is particularly crucial when dealing with domain-specific data, where the lexical senses and their meaning can completely differ from what a LLM has learned during its training stage. This paper investigates the following question: Do LLMs really adapt to domains and remain consistent in the extraction of structured knowledge, or do they only learn lexical senses instead of reasoning? To answer this question and, we devise a controlled experiment setup that uses WordNet to synthesize parallel corpora, with English and gibberish terms. We examine the differences in the outputs of LLMs for each corpus in two OL tasks: relation extraction and taxonomy discovery. Empirical results show that, while adapting to the gibberish corpora, off-the-shelf LLMs do not consistently reason over semantic relationships between concepts, and instead leverage senses and their frame. However, fine-tuning improves the performance of LLMs on lexical semantic tasks even when the domain-specific terms are arbitrary and unseen during pre-training, hinting at the applicability of pre-trained LLMs for OL.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2407.19998")
get_code_for_paper("2407.19998")
have("2407.19998")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2407.19998.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2407.19998.svg)](https://syntology.ai/paper/2407.19998)

Connect an agent — have() is free.