![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Large Language Models](https://towardsdatascience.com/category/artificial-intelligence/large-language-models/) # Your LLM Can Return Perfect JSON and Still Be Wrong What I learned after thinking more carefully about Structured Outputs on messy, incomplete data [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) August 31, 20268 min read ![](../images/000.jpg) Photo by Şahin Sezer Dinçer via [Pexels](https://www.pexels.com/photo/spiral-staircase-with-blue-glass-window-3676619/) Three weeks after I turned on [Structured Outputs](https://platform.openai.com/docs/guides/structured-outputs) for a pipeline that parsed payment confirmation messages into transaction records, I noticed that our reconciliation job started flagging a small, steady stream of mismatches. They were not crashes, and not malformed rows either. Just transactions where the amount and sender matched perfectly but the date was off. Something like 2 to 3% of a given week's volume, enough to notice, not enough to be obvious right away. At first I assumed that it was a timezone bug. But it wasn't. When I pulled the raw source messages next to the extracted records, a pattern showed up: every mismatched transaction came from a message that never mentioned a date at all. Something like "Payment received from Chinedu, ₦45,000, ref TXN-82K91." No date anywhere in the text. And the model had filled `transaction_date` in anyway, almost always the date the extraction job ran, off by less than an hour. The schema said `transaction_date: date`, required. The model couldn't return nothing. So it didn't. I'd been treating "the JSON is valid" as the finish line for this pipeline, and for weeks it looked like one. It isn't. It's the point where a quieter kind of failure becomes possible, one that never throws an error or fails a type check, and doesn't show up until something downstream depends on the value being real. Most of what gets written about Structured Outputs stops at "it can't return broken JSON anymore," as if that settles the reliability question. It settles one version of it. Learn this step by step with the interactive [AI Engineer](https://roadmap.sh/ai-engineer) roadmap. ## The trap of the perfect schema Structured Outputs solve a real problem. Before native schema enforcement, getting reliable JSON out of an LLM meant regex parsers, retry loops, and prompts that basically begged the model: "ONLY output JSON, no markdown, no preamble." With the modern OpenAI Python SDK and a Pydantic model, most of that category of pain just goes away: python ``` import logging from datetime import date from pydantic import BaseModel from openai import OpenAI logger = logging.getLogger(__name__) client = OpenAI() class Transaction(BaseModel): sender: str amount: float transaction_id: str transaction_date: date document = """ Payment received from Chinedu. Amount: ₦45,000 Reference: TXN-82K91 Date: 11 August 2026 """ # gpt-4o-mini kept merging the amount and reference into one field on # messages with unusual formatting, so this stays on the full model # despite the cost. Worth revisiting once mini catches up. completion = client.beta.chat.completions.parse( model="gpt-4o", messages=[ {"role": "system", "content": "Extract the transaction details."}, {"role": "user", "content": document}, ], response_format=Transaction, ) txn = completion.choices[0].message.parsed logger.info("parsed txn %s", txn.transaction_id) ``` Run it against a clean message and it works exactly as advertised. Every key present, every type correct, no try/except needed just to catch a stray markdown fence around the JSON. Then someone forwards you a message like this one: python ``` document = """ Payment received from Chinedu. Amount: ₦45,000 Reference: TXN-82K91 """ # No date in this one. ``` but the schema doesn't care that the date isn't there. It's still marked required, so something has to fill that slot, and it's never going to be the schema that bends. The model reaches for whatever gets it to a valid value instead: the current date, the training cutoff, a plausible-looking guess. What comes back type-checks perfectly. It's also completely made up, and there's nothing in the response itself that tells you which fields are which. ## Designing schemas for uncertainty The fix is a mental shift more than a code change. An empty field isn't an error in extraction, it's often just the truth. Making fields nullable takes the pressure off the model to invent something: python ``` class Transaction(BaseModel): sender: str | None amount: float | None transaction_id: str | None transaction_date: date | None ``` Now if the date's missing, the model can just say so. This also brings a distinction that's easy to blur, which is extraction versus inference. Extraction is "tell me exactly what's in the text." While inference is "tell me what it implies." A message that says "paid on Tuesday" and a schema demanding an ISO date, that's inference, whether you meant to ask for it or not. Sometimes inference is exactly what you want, but the decision should be yours, not something the model makes for you by default. A nullable field hands that decision back to your own code: python ``` if transaction.transaction_date is None: request_missing_info(transaction_id=transaction.transaction_id) ``` ## Evidence and provenance Nullable fields fix the "inventing values from nothing" problem. They don't fix the other one, which is honestly worse: the model gives you a value, and you have no way to tell if it actually read that value off the page or pattern-matched its way there. With a normal chat response you can at least watch it reason its way to an answer. Structured Outputs skip straight to the final form. So I started asking for a second field alongside every value, the exact chunk of source text that supposedly backs it up. python ``` from pydantic import Field class Extracted(BaseModel): """Generic wrapper so I'm not writing a near-identical class per field type.""" value: float | date | str | None evidence: str | None = Field(description="exact quote backing this value, empty if not found") class Transaction(BaseModel): sender: str | None amount: Extracted transaction_id: str | None transaction_date: Extracted ``` The generic `Extracted` wrapper is a shortcut, not a best practice. `value` is now a union type instead of a clean `float`, which costs some of the type safety the original schema had. That trade is worth it once a schema has more than a couple of field types, writing `ExtractedFloat`, `ExtractedDate`, `ExtractedString` separately is just busywork at that point. For one or two fields, keep the specific classes, they're usually cleaner. The pattern earns its keep two ways. Ordering `evidence` before `value` matters because keys generate in sequence, so the model has to write down what it's looking at before committing to an answer, a small forced show-your-work. And it gives a reviewer something concrete to check without re-reading the source. If `value` is filled in but `evidence` is empty, or contains text that isn't in the source anywhere, that mismatch is the hallucination showing up in the data itself. It doesn't come free. On a batch of a few hundred transaction messages, adding evidence fields across the schema pushed output tokens up by roughly a third, and latency rose enough to matter at pipeline scale. Not worth it for a five-digit zip code. But for a financial figure someone's going to act on, it's definitely worth it. ## The boundary between generation and validation By this point the schema is carrying a lot: nullable types so it doesn't invent things, evidence fields so I can catch it when it does anyway. But there's a whole category of wrongness neither of those touches, which is whether the value makes any sense as a fact about the world. The schema guarantees `amount` is a float. It says nothing about whether that float is negative, or whether `transaction_date` is somehow three days from now. Early on I tried fixing this in the prompt, with instructions like "the amount must be greater than zero," which in hindsight was a strange thing to ask a language model to enforce. It's not a calculator. A validator does this exactly right, every single time, for free: python ``` from pydantic import model_validator, ValidationError class Transaction(BaseModel): sender: str | None amount: float | None transaction_id: str | None transaction_date: date | None @model_validator(mode="after") def check_sane_values(self) -> "Transaction": # negative amounts have shown up exactly twice, both times because # the source message described a refund, not a payment if self.amount is not None and self.amount <= 0: raise ValueError(f"amount must be positive, got {self.amount}") if self.transaction_date is not None and self.transaction_date > date.today(): raise ValueError(f"transaction_date {self.transaction_date} is in the future") return self ``` So now the API is guaranteeing structure the moment it generates the response, and [Pydantic](https://docs.pydantic.dev/) is guaranteeing the data makes sense the moment it's parsed into the object, the same way every time, no LLM involved in that second check at all. When the validator throws, you've got options: kick the record to a human, or hand the exact error back to the model and let it try again. I went with the second one, capped hard at two retries: python ``` MAX_RETRIES = 2 def extract_with_retry(document: str) -> Transaction: history = [ {"role": "system", "content": "Extract the transaction details."}, {"role": "user", "content": document}, ] for attempt in range(MAX_RETRIES + 1): completion = client.beta.chat.completions.parse( model="gpt-4o", messages=history, response_format=Transaction ) raw = completion.choices[0].message.content try: return Transaction.model_validate_json(raw) except ValidationError as e: if attempt == MAX_RETRIES: raise # give up, let the caller route this to a human logger.warning("validation failed on attempt %d: %s", attempt, e) history += [ {"role": "assistant", "content": raw}, {"role": "user", "content": f"That failed validation: {e}. Fix only the bad field."}, ] ``` The `MAX_RETRIES` cap actually matters more than it looks. My first instinct was to let it keep trying, which is a mistake. Two failed attempts almost always means the source document is the actual problem, not the prompt, and a third automated pass just burns API calls on something a human clears in ten seconds. None of this is OpenAI-specific either, even though every code block here is. Swap in [Anthropic's tool use](https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview) or a self-hosted setup with [vLLM](https://docs.vllm.ai/en/latest/features/structured_outputs.html) and [Outlines](https://github.com/dottxt-ai/outlines) and the Pydantic model doesn't move an inch, it's just the API call around it that changes. ## Rethinking the goal of extraction When I first got this working, my bar for success was embarrassingly low: did the model fill out the object without breaking my parser. Looking back, that bar rewards the wrong thing entirely, because a model that eagerly fills every field regardless of what's actually in front of it isn't reliable. It's just confident, which is a different and more dangerous thing. Structured Outputs are genuinely good at what they do. They just don't do the thing I originally thought they did. They guarantee shape, not truth, and once you stop worrying about brackets and quote escaping, the real question is still sitting there waiting: does every value in this object have an actual reason to exist? That question was always the hard part. The schema just used to hide it from me. ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-4ad89a2fc5e69dde007d.jpeg) Written By ## [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) Benjamin Nweke is a Computer Science graduate and technical writer exploring AI, machine learning, and data science. He writes about building reliable AI systems, model evaluation, agentic architectures, and the practical challenges that appear when machine learning moves beyond experiments. His work focuses on making technically complex ideas clear, useful, and grounded in real implementation. [See all from Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) [Data Engineering](https://towardsdatascience.com/tag/data-engineering/)[Json](https://towardsdatascience.com/tag/json/)[Pydantic](https://towardsdatascience.com/tag/pydantic/)[Python](https://towardsdatascience.com/tag/python/)[Structured Output](https://towardsdatascience.com/tag/structured-output/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fyour-llm-can-return-perfect-json-and-still-be-wrong%2F&title=Your%20LLM%20Can%20Return%20Perfect%20JSON%20and%20Still%20Be%20Wrong) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fyour-llm-can-return-perfect-json-and-still-be-wrong%2F&title=Your%20LLM%20Can%20Return%20Perfect%20JSON%20and%20Still%20Be%20Wrong) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fyour-llm-can-return-perfect-json-and-still-be-wrong%2F&text=Your%20LLM%20Can%20Return%20Perfect%20JSON%20and%20Still%20Be%20Wrong) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/001.jpg)](https://towardsdatascience.com/a-new-method-to-detect-confabulations-hallucinated-by-large-language-models-19444475fc7e/) ## [A New Method to Detect "Confabulations" Hallucinated by Large Language Models](https://towardsdatascience.com/a-new-method-to-detect-confabulations-hallucinated-by-large-language-models-19444475fc7e/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) By calculating semantic entropy with a second LLM, we can better flag answers as unreliable due to lack of knowledge [Luciano Abriata](https://towardsdatascience.com/author/lucianosphere/) June 25, 202410 min read * [![](../images/002.jpeg)](https://towardsdatascience.com/a-quick-way-to-build-applications-in-python-51d5ef477d88/) ## [A Quick Way to Build Applications in Python](https://towardsdatascience.com/a-quick-way-to-build-applications-in-python-51d5ef477d88/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Build MVPs with a few lines of code [Naser Tamimi](https://towardsdatascience.com/author/tamimi-naser/) February 8, 20216 min read * [![](../images/003.jpg)](https://towardsdatascience.com/how-to-find-the-best-multilingual-embedding-model-for-your-rag-40325c308ebb/) ## [How to Find the Best Multilingual Embedding Model for Your RAG](https://towardsdatascience.com/how-to-find-the-best-multilingual-embedding-model-for-your-rag-40325c308ebb/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Optimize the Embedding Space for Improving RAG [Iulia Brezeanu](https://towardsdatascience.com/author/brezeanu.iulia/) January 27, 20248 min read * [![](../images/004.png)](https://towardsdatascience.com/hands-on-attention-mechanism-for-time-series-classification-with-python/) ## [Hands-On Attention Mechanism for Time Series Classification, with Python](https://towardsdatascience.com/hands-on-attention-mechanism-for-time-series-classification-with-python/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) This is how to use the attention mechanism in a time series classification framework [Piero Paialunga](https://towardsdatascience.com/author/piero-paialunga/) May 30, 20258 min read * [![](../images/005.jpg)](https://towardsdatascience.com/python-module-for-easy-data-pre-processing-for-beginners-40f0f6b407a8/) ## [Python Module for easy data pre-processing for beginners](https://towardsdatascience.com/python-module-for-easy-data-pre-processing-for-beginners-40f0f6b407a8/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) There is a need to process these data quickly and create an initial model to better understand your dataset or the problem at hand. [Benjamin Lau](https://towardsdatascience.com/author/ben_lau93/) January 31, 20194 min read * [![](../images/006.png)](https://towardsdatascience.com/data-analytics-with-python-by-web-scraping-illustration-with-cia-world-factbook-abbdaa687a84/) ## [Data Analytics with Python by Web scraping: Illustration with CIA World Factbook](https://towardsdatascience.com/data-analytics-with-python-by-web-scraping-illustration-with-cia-world-factbook-abbdaa687a84/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) In this article, we show how to use Python libraries and HTML parsing to extract useful information from a website and build analytics. [Tirthajyoti Sarkar](https://towardsdatascience.com/author/tirthajyoti/) March 4, 20189 min read * [![](../images/007.png)](https://towardsdatascience.com/time-series-are-not-that-different-for-llms-56435dc7d2b1/) ## [Time Series Are Not That Different for LLMs](https://towardsdatascience.com/time-series-are-not-that-different-for-llms-56435dc7d2b1/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Harnessing the power of LLMs for time series modeling [Henry Lai](https://towardsdatascience.com/author/a0987284901/) July 12, 20247 min read * [![](../images/008.jpeg)](https://towardsdatascience.com/function-wrappers-in-python-5146f3ad0601/) ## [Function Wrappers in Python](https://towardsdatascience.com/function-wrappers-in-python-5146f3ad0601/) [Programming](https://towardsdatascience.com/category/programming/) Putting a Wrapper Around a Function [Sadrach Pierre, Ph.D.](https://towardsdatascience.com/author/spierre91/) May 5, 20205 min read * [![](../images/009.jpg)](https://towardsdatascience.com/chinese-postman-in-python-8b1187a3e5a/) ## [Chinese Postman in Python](https://towardsdatascience.com/chinese-postman-in-python-8b1187a3e5a/) [Programming](https://towardsdatascience.com/category/programming/) Detailed Implementation & Explanation, with special emphasis on unique approach to generate Odd Vertex Pairings using Recursion [Araz Sharma](https://towardsdatascience.com/author/arazsharma1103/) November 9, 20201 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ "How Relevance Models Foreshadowed Transformers for NLP") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?")