Papers › LLM Blueprint: Enabling Text-to-Image Generation with Complex and Detailed Prompts

LLM Blueprint: Enabling Text-to-Image Generation with Complex and Detailed Prompts

16 Oct 2023arXiv:2310.10640archive 2025-07-28

Hanan Gani, Shariq Farooq Bhat, Muzammal Naseer, Salman Khan, Peter Wonka

Diffusion-based generative models have significantly advanced text-to-image generation but encounter challenges when processing lengthy and intricate text prompts describing complex scenes with multiple objects. While excelling in generating images from short, single-object descriptions, these models often struggle to faithfully capture all the nuanced details within longer and more elaborate textual inputs. In response, we present a novel approach leveraging Large Language Models (LLMs) to extract critical components from text prompts, including bounding box coordinates for foreground objects, detailed textual descriptions for individual objects, and a succinct background context. These components form the foundation of our layout-to-image generation model, which operates in two phases. The initial Global Scene Generation utilizes object layouts and background context to create an initial scene but often falls short in faithfully representing object characteristics as specified in the prompts. To address this limitation, we introduce an Iterative Refinement Scheme that iteratively evaluates and refines box-level content to align them with their textual descriptions, recomposing objects as needed to ensure consistency. Our evaluation on complex prompts featuring multiple objects demonstrates a substantial improvement in recall compared to baseline diffusion models. This is further validated by a user study, underscoring the efficacy of our approach in generating coherent and detailed scenes from intricate textual inputs.

PaperPDFCodeCode Syntology ran

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 12 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 12 samples from 1 repository, 10 ran (7 with no instrument failure; 3 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.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 10 samples that ran has no recorded date.

hananshafi/llmblueprint officialmentioned in papermentioned on GitHubpytorchSyntology: 12 samples, 10 ran (3 instrument-failed) · 2 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.

Code Syntology ran Syntology

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

3ran · our draft was wrong
7ran
2unverified

Licence: 12 of the 12 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 hananshafi/llmblueprint. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

hananshafi/llmblueprint official repository 12 samples, 10 ran (3 instrument-failed) · 2 unverified
chunk in 52 papers composition_module/my_paint_by_example.py ran · our draft was wrong no licence file found · pointer only · 8241c0562bc710fd · report fixture: signature it:list/1/int, size:int/0/int · returned callable_iterator · level recorded, date not recorded
create_square_mask helper_functions.py ran no licence file found · pointer only · 004fbf7e9634c634 · report fixture: signature image:Image/0/?, bbox:tuple/1/int · returned Image · level recorded 2026-09-24
crop_image in 17 papers composition_module/my_paint_by_example.py ran no licence file found · pointer only · cf4b29877ff87f73 · report fixture: signature img:Tensor/4/float, bbox:list/1/int · returned Tensor · level recorded 2026-09-24
crop_with_mask helper_functions.py ran no licence file found · pointer only · d9a135a826e1cd55 · report fixture: signature image:ndarray/3/int, mask:ndarray/2/int · returned ndarray · level recorded 2026-09-24
decode in 57 papers models/pipelines.py ran no licence file found · pointer only · 3f195c728018813a · report fixture: signature vae:callable/0/?, latents:Tensor/4/float · returned ndarray · level recorded 2026-09-24
get_parameter_device in 18 papers models/modeling_utils.py ran no licence file found · pointer only · e62fd44647fe3180 · report fixture: signature parameter:callable/0/? · returned device · level recorded 2026-09-24
get_parameter_dtype in 20 papers models/modeling_utils.py ran no licence file found · pointer only · f2cf0722edfc04f0 · report fixture: signature parameter:callable/0/? · returned dtype · level recorded 2026-09-24
get_tensor_clip composition_module/my_paint_by_example.py ran · our draft was wrong no licence file found · pointer only · d34c20f0713a7951 · report fixture: signature normalize:bool/0/bool, toTensor:bool/0/bool · returned Compose · level recorded 2026-09-24
increase_bbox_size helper_functions.py ran no licence file found · pointer only · 7002baa29d797c3a · report fixture: signature bbox:list/1/int, padding:int/0/int · returned tuple · level recorded 2026-09-24
process_input_embeddings models/models.py ran · our draft was wrong no licence file found · pointer only · 2f1664cb838533c9 · report fixture: signature input_embeddings:list/1/Tensor · returned tuple · level recorded 2026-09-24
encode in 73 papers models/pipelines.py unverified no licence file found · pointer only · 57dcb958e30899c0 · report

Tasks

Image GenerationLayout-to-Image GenerationObjectScene GenerationText to Image GenerationText-to-Image Generation

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

ALIGNDiffusion

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