SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2203.10940 · ACL · 2022

Quality Controlled Paraphrase Generation

Noam Slonim, Ranit Aharonov, Elron Bandel, Ilya Shnayderman, Liat Ein-Dor, Michal Shmueli-Scheuer

arXiv · PDF · Open in the Atlas

Code that ran

5 of 6 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 2 have no contract verdict; 3 failures of our instrument; 1 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/2203.10940.json · badge: /api/ran/2203.10940.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
ibm/quality-controlled-paraphrase-generation canonical (classifier label)
classifier basis not recorded on the link
5 ran · 1 no recorded run
FunctionStatusWhere it lives
bad_chars_filter Ran
ran; our contract draft was wrong, not the code
ibm/quality-controlled-paraphrase-generation/data.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from astro-jon/LCWL, is pointer only (licence: NONE) · get_code("5fad151c1668eb5c")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from astro-jon/LCWL, and GitHub detected no licence in that repository when it was checked. 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.

extract_suffix Ran
ran; our contract draft was wrong, not the code
ibm/quality-controlled-paraphrase-generation/data.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from astro-jon/LCWL, is pointer only (licence: NONE) · get_code("48e750826b962e43")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from astro-jon/LCWL, and GitHub detected no licence in that repository when it was checked. 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.

normalize_tree Ran
ran on a synthesized input
ibm/quality-controlled-paraphrase-generation/metrics/syntdiv_metric/syntdiv_metric.py
code served (permissive licence) · get_code("8f54e370669cd581")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned str. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Analyze the function:
# - tree_string: a string parameter that gets iterated character by character
# - max_depth: an integer parameter with default value 3

# The function processes tree_string looking for characters like '{', '}', '(', ')', ' '
# and builds a result based on depth tracking and leaf status

# Create valid test cases
tree_string_1 = "( a ( b ) )"
tree_string_2 = "{ ( x ( y ) ) }"
max_depth_1 = 3
max_depth_2 = 2

ARGS = {
    "tree_string": "( a ( b ( c ) ) )",
    "max_depth": 3
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type str — a str output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a str output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
remove_non_printables Ran
ran; our contract draft was wrong, not the code
ibm/quality-controlled-paraphrase-generation/data.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from astro-jon/LCWL, is pointer only (licence: NONE) · get_code("ea58b0626fa1cc01")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from astro-jon/LCWL, and GitHub detected no licence in that repository when it was checked. 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.

to_batches Ran
ran on a synthesized input
ibm/quality-controlled-paraphrase-generation/metrics/bleurt/bleurt.py
code served (permissive licence) · get_code("ca038c1d5766ac3b")
How it ran

Ran in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned generator. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.

import torch
import numpy as np

torch.manual_seed(0)

# Analyze the function: to_batches(seq, size)
# - seq: needs len() and slicing [pos:pos + size]
# - size: an integer for batch size
# The function iterates through seq in chunks of size

# Create a simple sequence - a list works well
seq = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]

# Create a batch size
size = 3

ARGS = {
    "seq": seq,
    "size": size
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type generator — a generator output has no array shape of its own; none is stated — the instrument coerces any output to an array; for a generator output the recorded ndim 0 and dtype family float describe that coercion, not the output, and are not stated
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
normalize_condition Not yet run
unverified (harvested, no recorded run)
ibm/quality-controlled-paraphrase-generation/QCPG/predict.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from astro-jon/LCWL, is pointer only (licence: NONE) · get_code("842c16c796122961")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from astro-jon/LCWL, and GitHub detected no licence in that repository when it was checked. 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 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 distinct functions with an identity, 4 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 4 later) and 2 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.

FunctionAlso present inEarliest-datedOthers named
bad_chars_filter 1 other paper
1 later
2410.05748 (2024-10)
Label Confidence Weighted Learning for Target-level Sentence Simplification
extract_suffix 1 other paper
1 later
2410.05748 (2024-10)
Label Confidence Weighted Learning for Target-level Sentence Simplification
normalize_condition 1 other paper
1 later
2410.05748 (2024-10)
Label Confidence Weighted Learning for Target-level Sentence Simplification
remove_non_printables 1 other paper
1 later
2410.05748 (2024-10)
Label Confidence Weighted Learning for Target-level Sentence Simplification

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

Paraphrase generation has been widely used in various downstream tasks. Most tasks benefit mainly from high quality paraphrases, namely those that are semantically similar to, yet linguistically diverse from, the original sentence. Generating high-quality paraphrases is challenging as it becomes increasingly hard to preserve meaning as linguistic diversity increases. Recent works achieve nice results by controlling specific aspects of the paraphrase, such as its syntactic tree. However, they do not allow to directly control the quality of the generated paraphrase, and suffer from low flexibility and scalability. Here we propose QCPG, a quality-guided controlled paraphrase generation model, that allows directly controlling the quality dimensions. Furthermore, we suggest a method that given a sentence, identifies points in the quality control space that are expected to yield optimal generated paraphrases. We show that our method is able to generate paraphrases which maintain the original meaning while achieving higher diversity than the uncontrolled baseline. The models, the code, and the data can be found in https://github.com/IBM/quality-c ontrolled-paraphrase-generation.

For agents

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

get_harvested_code_for_paper("2203.10940")
get_code_for_paper("2203.10940")
have("2203.10940")

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

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

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

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

Connect an agent — have() is free.