Microsoft · Filed Feb 28, 2025 · Published Sep 3, 2026 · verified — real USPTO data

Microsoft Patents an AI That Converts Fuzzy Date Phrases Into Exact Calendar Dates

When you type 'show me files from last quarter' into a search bar, a computer has to figure out what 'last quarter' actually means on a calendar. Microsoft has filed a patent for an AI system designed to do exactly that, automatically and accurately.

An AI system processes an input query to extract temporal information and classify it into a precise start and end date. Drawing from patent filing US 2026/0259889 A1.
An AI system processes an input query to extract temporal information and classify it into a precise start and end date.
See all 8 drawings from this filing ↓
Publication number US 2026/0259889 A1
Applicant Microsoft Technology Licensing, LLC
Filing date Feb 28, 2025
Publication date Sep 3, 2026
Inventors Justin James WAGLE, Sunando SENGUPTA, Rajath Kumar RAVI
CPC classification 707/736
Grant likelihood Medium
Examiner SINGH, AMRESH (Art Unit 2159)
Status Final Rejection Mailed (May 15, 2026)
Document 20 claims

What Microsoft's date-reading AI actually does

Imagine typing 'meetings from the week before the holiday' into your company's search tool. A human knows what that means. A computer, until recently, mostly didn't.

Microsoft's patent describes a three-step AI system that reads the date-related words in your search, figures out what they mean in context, and converts them into a specific day, month, and year. It handles fuzzy, natural phrases like 'next Monday,' 'early spring,' or 'two weeks ago' and turns them into something a database can actually use.

The system works by first spotting the date-related part of your question, then computing the meaning of that phrase, and finally classifying it into a precise calendar date. The output gets passed along to whatever search or scheduling tool needs it.

How the model maps language to a day, month, and year

The patent describes a pipeline of three machine learning models working in sequence.

Step one is a query parsing model that reads your full input and picks out the part that refers to time. So from 'show me invoices from late January,' it would extract 'late January' as the relevant fragment.

Step two is a sentence embedding model (a system that converts words into a dense grid of numbers that captures meaning). This model turns the extracted date phrase into a numerical representation the next model can work with.

Step three is the core invention: a date classifier model that takes that numerical representation and expands the part of it that encodes date-related meaning, a process the patent calls 'upscaling an embedding space region.' Think of it like zooming in on the section of a map that covers the territory you care about. After that zoom, the model runs classification (essentially a structured multiple-choice decision) to pin down a specific day, month, and year.

The final output, a fully resolved calendar date, gets passed to whatever downstream system needs it: a search index, a calendar app, a scheduling tool.

What this means for search and scheduling tools

For everyday users, this is the difference between a search bar that understands you and one that makes you remember to type '01/20/2025' instead of 'last Martin Luther King Day.' If this system works well, tools like Microsoft 365's search, Outlook, or Teams would handle vague date references the way a helpful assistant would.

Microsoft's ongoing push into natural-language search The harder question is whether the system generalizes across cultures and languages, where date references are wildly different. 'Diwali week,' 'Golden Week,' or 'the fiscal year-end' mean different things depending on where you are. The patent doesn't specifically address localization, which is where this approach would face its biggest real-world test.

Microsoft's 51st filing in the Language AI work we've tracked since May adds to a run that includes one turning prompts into layered art and one writing chart code from scratch.

Editorial take

The core design trade-off here is specificity versus flexibility. The model is trained to output a precise date: a day, a month, a year. That precision is useful downstream, but it forces the system to commit even when the input phrase is genuinely ambiguous. 'Early spring' in a business context might mean a date range, not a single day, and collapsing it to one calendar point could produce wrong results without any visible error.

The 'upscaling' step, where the model zooms in on the date-relevant portion of the word embedding, is the genuinely interesting design choice. It suggests the team found that general-purpose language models spread their attention too thin on date semantics, and that forcing focus on that region improves accuracy. That's a reasonable engineering bet, but it also means the model is being tuned narrowly, which could make it brittle against unusual phrasing or non-Western calendar references.

For a company that runs productivity software used by hundreds of millions of people, getting date parsing right is important and genuinely underserved. This filing reads as a practical, infrastructure-level fix rather than a flashpoint invention.

There are more where this came from

We read every patent application Big Tech publishes and send you the ones worth knowing. Plain English, free, every week.

The drawings

8 drawing sheets from US 2026/0259889 A1 · click any drawing to enlarge

Patent filing page

Source. Full patent text and figures from the official USPTO publication PDF.