In 2004, long before ChatGPT, large language models, or the current generative AI boom, I served as project lead and technical lead on a university and government research initiative built around a deceptively simple question: Why should someone have to understand how a database works to get an answer from it? At the time, sophisticated information systems generally required specialized interfaces, predefined reports, query languages, or help from someone in Information Technology. Storing information was increasingly inexpensive, but accessing it often meant understanding how someone else had organized the data. In short, findability was the hard part.
We wanted to make that easier.
Instead of forcing people to learn a computer system’s language and structure, we wanted the system to adapt to how people naturally communicate. We built a working architecture that combined speech recognition, natural language processing, semantic models, text-to-speech, wireless devices, and contextual information from technologies such as radio-frequency identification and GPS. A user could ask a question in ordinary English; the system would determine what the person meant, translate that request into a database operation, retrieve the relevant information, and return a direct answer, potentially by voice and without the user ever seeing a conventional computer interface.
One of our first demonstrations was a virtual museum docent. A visitor could stand near a work of art and ask questions about it. Because the system knew the visitor’s proximity to a particular artwork, the spoken question didn't need to include every piece of information needed to answer it. The software could combine the words with external context to determine which object the visitor meant. The original proof of concept was built in 2004 and publicly demonstrated the following year.
The underlying technology was very different from today’s transformer-based generative AI, and I do not regard it as an early version of ChatGPT. It was not a large language model, a generative AI system, an agent, or a retrieval-augmented generation system. What strikes me in retrospect is something more interesting: many of the practical problems we were trying to solve are the same ones developers face today when they try to turn an impressive AI model into a reliable, useful system.
The models changed dramatically. Many of the underlying problems did not.
Context matters as much as language
Human language is inherently ambiguous. Meaning depends not just on words, but on context, specialized terminology, prior interactions, location, and shared assumptions. Our approach relied heavily on semantic models that represented the particular business or application domain. We deliberately constrained the domain rather than trying to solve the entire problem of understanding human language, making the system more accurate, more predictable, and much more practical to deploy. We considered daisy-chaining several domain-specific systems into a larger, more powerful whole, but never got around to it.
Modern large language models start from an extraordinarily more capable foundation, but applied AI still depends heavily on supplying the right context. Today’s terminology includes grounding, retrieval, persistent context, domain knowledge, memory, and knowledge architectures. The mechanisms have changed, but the practical question is recognizable: What information does the system need in order to understand what this person means in this particular situation?
A second challenge was turning language into action. We distinguished what we called discrete answer retrieval from conventional document retrieval. If someone asks, “Who are our top ten customers?”, the desired result is not a collection of documents that may contain the answer. The system has to understand the request, map the language to the underlying data model, construct the appropriate database query, execute it, and return the answer. Our platform was explicitly designed to translate natural-language concepts into operations against structured information systems.
This parallels today’s AI systems that translate a user’s request into database queries, searches, application actions, or tool calls. I would not equate the technologies; current models can operate across language and information in ways that were simply unavailable to us. But the architectural problem, moving from what the user says to what the system should do, is essentially the same.
We also concluded early that language alone was sometimes insufficient. One idea that emerged from the project, and later became part of our patent portfolio, was to combine a natural-language request with information from other sources. Location and proximity were obvious examples. If someone standing in front of an object asks, “Who made this?”, the word this is meaningless unless the system can understand the surrounding context. We used RFID tags attached to paintings to establish proximity.
That led us toward a multimodal architecture. Voice, location, RFID, GPS, and other environmental inputs could all help interpret the request. The goal was not simply better speech recognition. It was better intent understanding by combining what a person said with what the system knew about the situation.
Today’s multimodal AI systems can work with language, images, audio, application state, external data, location, and other forms of context on a scale we could not have approached in 2004. Yet one central design question remains unchanged: Which pieces of context should the system consider, and how should they influence its interpretation of what the user wants?
We also had to decide what happened when the machine was wrong
No semantic model could anticipate every question. Rather than assuming the system would always understand, we designed around failure. If it understood most of a request but encountered an ambiguous portion, it could ask the user for clarification. If it could not resolve the problem itself, a human could step in. We also considered retaining successful interactions and regression-testing them after semantic-model changes so that fixing one problem did not silently break answers that had previously worked.
In another proposed application, the system would automatically resolve requests the natural-language engine could handle confidently, while routing harder cases to a conventional human customer-service workflow. The expectation was that the proportion handled automatically would increase as the technology, semantic model, and knowledge repository improved.
Today we use terms such as human-in-the-loop, escalation, confidence thresholds, evaluation, regression testing, and continuous improvement. The vocabulary is newer, and the systems are immeasurably more capable, but the operational lesson is familiar: useful AI is not simply about producing an answer. It also requires knowing when the answer may not be good enough, testing the system systematically, and deciding when people need to remain involved.
The work led to four U.S. patents
That work led to four issued U.S. patents in multimodal natural-language query technology, on which I was the named inventor: U.S. Patent Nos. 7,376,645; 7,873,654; 8,150,872; and 9,223,776.[1] The first patent claims priority to November 29, 2004, was filed on January 24, 2005, and was issued on May 20, 2008. The later grants extend the portfolio through continuation applications and later claims.
I value that work today not because it proves that we somehow foresaw large language models (we did not). I value it because it offers a useful perspective on how much has changed, and how much has not. The long-standing ambition has been to make computers understand what people actually want without forcing people to learn how computers represent the world. What has changed is our ability to get much closer to that goal.
From custom language systems to modern AI
In 2004, accomplishing even a relatively constrained version of this required considerable custom engineering. We had to worry about recognition grammars, semantic models, application-specific vocabularies, database schemas, speech technologies, integration, and specialized logic. Our planning materials called for continuing work on semantic models, statistical language techniques, scalability, administration tools, metrics, security, and exception handling.
Modern foundation models greatly reduce the custom language engineering required to get started. A capable general-purpose model can start with linguistic abilities that once would have required a major development effort. That changes the economics of the problem enormously. It also shifts much of the difficult applied work away from building the language capability itself and toward the architecture surrounding the model.
Technological progress often looks discontinuous from a distance. A new capability suddenly becomes visible, adoption accelerates, and it seems the world changed almost overnight. But what looks like a step change often reflects decades of iterative work that crosses several thresholds at roughly the same time. Algorithms improve. Compute becomes more capable. Specialized hardware makes certain calculations practical. Data becomes more abundant and better organized. Cloud infrastructure makes capacity easier to obtain. Software frameworks reduce the cost of experimentation. Interfaces make the capability legible to ordinary users. Business models give firms a reason to keep investing, deploying, and improving.
Generative AI is a striking example, but the sequence was neither automatic nor inevitable. Large labeled datasets such as ImageNet made it possible to compare systems at a scale that smaller datasets could not support.[2] AlexNet’s 2012 result combined a deep neural network, a large dataset, and efficient GPU implementation to deliver a measurable performance gain.[3] NVIDIA introduced CUDA in 2006, making GPU throughput more accessible to general-purpose software.[4] The 2017 transformer architecture relied on attention rather than recurrence and was designed to be more parallelizable.[5] GPT-3 then showed how performance and few-shot behavior could change with much greater model scale, while also documenting important limitations in training data and evaluation.[6]
The surrounding ecosystem changed too. Amazon EC2’s 2006 beta offered resizable computing capacity billed by use rather than requiring every developer to own the underlying servers.[7] TensorFlow’s 2015 open-source release and later frameworks lowered the cost of building, sharing, and deploying machine-learning systems.[8] In 2020, the OpenAI API offered a general text-in, text-out interface, allowing developers to incorporate model capability into products without building the base model themselves.[9] ChatGPT’s conversational research preview in November 2022 made a much more capable language interface directly accessible to a broad public and invited rapid feedback through ordinary use.[10] Those delivery models also gave developers and users practical ways to buy access without financing the entire technical stack themselves.
None of those events alone explains generative AI’s emergence at scale. Nor does the sequence prove that the outcome had to occur. Technical progress can stall; economics can fail; regulation, energy, supply chains, organizational readiness, trust, and user behavior can redirect what gets built. The better claim is cumulative and contingent: a visible step change can occur when technical capabilities and an economically viable delivery system become good enough together.
I have treated the physical, financial, and institutional side of that delivery system in The AI Industrial System.[11] The narrower point here is historical. The public breakthrough was real in its effects without being discontinuous in its origins. A model architecture mattered, but so did the semiconductor and cloud capacity that trained and served it; the datasets that shaped it; the software tools that let teams experiment; the interfaces that let people use it; and the business arrangements that funded the whole system. Isolating the exact contribution of each is difficult, and their interactions matter more than a single-cause story.
The questions I spend more time thinking about today are therefore not simply about model intelligence. They concern what context an AI should receive, which information sources it should trust, what tools it should be allowed to use, how we determine whether its answers are good enough, and when it should ask for clarification or escalate to a person. They also concern autonomy and evaluation: how much freedom should the system have, and how do we improve weak behavior without damaging what already works? For a business, all of this eventually reduces to another question: Does the resulting system create enough value to justify its cost, complexity, and risk?
Those are questions of applied AI and AI strategy, not simply model capability.
A principle that still holds
Looking back, one principle from that early work has held up particularly well: technology should adapt to the person rather than forcing the person to adapt to the technology. We described our objective then as letting subject-matter experts access sophisticated information in the language they already understood, without needing to know the database, query language, or software architecture underneath.
Today’s AI lets us take that idea far beyond anything we could build two decades ago. I am not nostalgic for the old technology; modern models are incomparably more capable. What interests me is the problem’s continuity. The models changed, the interfaces changed, and the economics changed, but people still know what they want to accomplish, and computers still need a mechanism to translate that human intention into something the machine can reliably do.
Applied AI increasingly makes that translation the machine’s problem rather than the user’s. That was what interested me in 2004, and it is a large part of what interests me again today. In that respect, 2026 looks surprisingly familiar from a 2004 perspective.
Source note
This essay draws on my experience leading the project, surviving technical and demonstration materials from 2004 through 2006, the resulting patent record, and primary sources on the later development of modern AI.
Questions, corrections, or disagreements are welcome. You can reach me directly at dave@aworkingmodel.com.
Sources
1. U.S. Patent Nos. 7,376,645, 7,873,654, 8,150,872, and 9,223,776, multimodal natural-language query patents, issued 2008, 2011, 2012, and 2015.
2. Jia Deng et al., “ImageNet: A Large-Scale Hierarchical Image Database,” CVPR 2009.
3. Alex Krizhevsky, Ilya Sutskever, and Geoffrey Hinton, “ImageNet Classification with Deep Convolutional Neural Networks,” NeurIPS 2012.
4. NVIDIA, CUDA Programming Guide, “Introduction.”
5. Ashish Vaswani et al., “Attention Is All You Need,” 2017.
6. Tom B. Brown et al., “Language Models are Few-Shot Learners,” 2020.
7. Amazon Web Services, “Announcing Amazon Elastic Compute Cloud (Amazon EC2) - beta,” August 24, 2006.
8. Google, “TensorFlow: smarter machine learning, for everyone,” November 9, 2015.
9. OpenAI, “OpenAI API,” June 11, 2020.
10. OpenAI, “Introducing ChatGPT,” November 30, 2022.
11. Dave Bernard, “The AI Industrial System,” A Working Model, September 2026.