Papers › Unified Structure Generation for Universal Information Extraction

Unified Structure Generation for Universal Information Extraction

23 Mar 2022ACL 2022 5arXiv:2203.12277archive 2025-07-28

Yaojie Lu, Qing Liu, Dai Dai, Xinyan Xiao, Hongyu Lin, Xianpei Han, Le Sun, Hua Wu

Information extraction suffers from its varying targets, heterogeneous structures, and demand-specific schemas. In this paper, we propose a unified text-to-structure generation framework, namely UIE, which can universally model different IE tasks, adaptively generate targeted structures, and collaboratively learn general IE abilities from different knowledge sources. Specifically, UIE uniformly encodes different extraction structures via a structured extraction language, adaptively generates target extractions via a schema-based prompt mechanism - structural schema instructor, and captures the common IE abilities via a large-scale pre-trained text-to-structure model. Experiments show that UIE achieved the state-of-the-art performance on 4 IE tasks, 13 datasets, and on all supervised, low-resource, and few-shot settings for a wide range of entity, relation, event and sentiment extraction tasks and their unification. These results verified the effectiveness, universality, and transferability of UIE.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 1 repository linked to this paper: 6 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 6 samples from 1 repository, 6 ran (2 with no instrument failure; 4 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

MS-P3/code5 mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Instruct-MusicGen: Unlocking Text-to-Music Editing for Music Language Models via... (arXiv:2405.18386; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
universal-ie/UIE pytorchSyntology: 6 samples, 6 ran (4 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

6 samples harvested: 6 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
2ran; the contract check could not run
2ran

Licence: 6 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from universal-ie/UIE. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

universal-ie/UIE community (archive-listed) 6 samples, 6 ran (4 instrument-failed) · 0 unverified
ConstraintDecoder uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran no licence file found · pointer only · 916de06919b6c4c7 · report fixture: returned ConstraintDecoder · level recorded 2026-09-22
SpotAsocConstraintDecoder uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran no licence file found · pointer only · aa69a0605f7fd045 · report fixture: returned SpotAsocConstraintDecoder · level recorded 2026-09-22
find_bracket_position uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran · our draft was wrong fingerprinted no licence file found · pointer only · c2c95a98621f39bf · report fixture: signature generated_text:str/0/str, _type_start:str/0/str, _type_end:str/0/str · returned dict · level recorded 2026-09-22
generated_search_src_sequence uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed fingerprinted no licence file found · pointer only · 24bcd325baf8ba70 · report fixture: signature generated:list/1/int, src_sequence:list/1/int, end_sequence_search_tokens:NoneType/0/? · returned list · level recorded 2026-09-22
get_label_name_tree uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran · our draft was wrong no licence file found · pointer only · d07f851a6d8b7cba · report fixture: signature label_name_list:list/1/str, tokenizer:MinimalTokenizer/0/?, end_symbol:str/0/str · returned dict · level recorded 2026-09-22
match_sublist uie/seq2seq/constraint_decoder/spotasoc_constraint_decoder.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed no licence file found · pointer only · 038ce7a52b360c39 · report fixture: signature the_list:list/1/int, to_match:list/1/int · returned list · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for UIE (graph method: UIE). 6 bricks; individually on a fixture: 6 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 4 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. SpotAsocConstraintDecoder entry · level 1 · ran · aa69a0605f7fd045
  2. ConstraintDecoder helper · level 1 · ran · 916de06919b6c4c7
  3. find_bracket_position helper · level 1 · ran · our draft was wrong · c2c95a98621f39bf
  4. generated_search_src_sequence helper · level 1 · ran; the contract check could not run (RAISES) · 24bcd325baf8ba70
  5. get_label_name_tree helper · level 1 · ran · our draft was wrong · d07f851a6d8b7cba
  6. match_sublist helper · level 1 · ran; the contract check could not run (RAISES) · 038ce7a52b360c39

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2203.12277") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Aspect-Based Sentiment Analysis (ABSA)UIE

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Aspect-Based Sentiment Analysis (ABSA) ASTE UIE F1 (L14) 62.94 #5 of 13 Archive leaderboard report
Aspect-Based Sentiment Analysis (ABSA) ASTE UIE F1 (R15) 64.41 #5 of 13 Archive leaderboard report
Aspect-Based Sentiment Analysis (ABSA) ASTE UIE F1 (R16) 72.86 #5 of 13 Archive leaderboard report
Aspect-Based Sentiment Analysis (ABSA) ASTE UIE F1(R14) 72.55 #5 of 13 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections