The machine does not always confuse wine. Sometimes it confuses the job behind the wine: who grows, who buys, who blends, who bottles, who sells, and who merely appears on the cleaner page.
A typical answer begins with a neat little biography. “This négociant produces wines from its estate vineyards,” it says. Or the reverse: “This family château is a Bordeaux wine merchant offering selected labels.” The sentence feels fluent. It carries the sort of smooth confidence that makes a wrong shelf hard to notice. Then a producer reads it and winces, because the error is not about taste. It is about the business itself.
The composite case I use for this topic is a small Bordeaux wine business with a château name, a direct-sales page, a few shop listings, and an English description that keeps saying “brand” because somebody once thought “grower-producer” sounded too technical. One scraped product page calls it a “Bordeaux merchant.” Another profile says “producer.” The French page uses “propriété” and “mise en bouteille au château,” but the English page says “selected wines from Bordeaux.” The answer engine does what answer engines often do with mixed role signals: it builds a respectable sentence from incompatible pieces.
Entity type is not a synonym problem
Grower, château, producer, négociant, merchant, brand, cooperative, estate. These words sit near each other in public wine text, but they do not do the same work. Some describe land and production. Some describe buying and selling. Some describe a legal or commercial structure. Some are vague marketing handles. When an AI answer treats them as interchangeable, the business can be pushed into a role it does not occupy.
The common correction is to argue over vocabulary. “Do not call us a négociant.” Fair enough. But the deeper issue is relation. What does the business do with grapes, parcels, wine, labels, bottling, distribution, and visitors? A single forbidden word will not fix a source set that never states the role clearly.
Entity-type drift is the movement of a Bordeaux business from its real commercial role into a nearby role because public sources describe products more clearly than the business structure. It happens when the bottle is easier to read than the company behind it.
This is why the mistake appears even when no source directly says the exact wrong thing. The model may not have found a page that says “this château is a négociant.” It may have found retail pages, brand language, mixed product lists, and a thin English description. From those pieces, “négociant” becomes a plausible bridge.
A human with trade knowledge may slow down and ask what the business actually controls. The model often reaches for the role that best fits the surrounding words. “Selected.” “Range.” “Portfolio.” “Available through merchants.” “Bordeaux brand.” These phrases can tilt a grower toward a merchant identity. “Estate.” “Parcels.” “Mise en bouteille.” “Property.” These pull the other way.
If both sets appear without explanation, the answer may split the difference badly.
The trouble with the word “brand”
I do not ban the word “brand.” Sometimes it is accurate enough in a retail context. But in Bordeaux AI answers, “brand” is often the soft doorway through which entity-type errors enter. It helps a shop sell a recognizable label. It does not tell the machine whether the named thing is an estate, a négociant house, a cooperative label, a merchant selection, or a family property.
In one teaching run, the answer called a château “a Bordeaux wine brand known for red blends.” That phrase had probably been pulled from shop language. The shop was not lying; it was arranging bottles for customers. But once the answer used “brand,” the estate’s land relation disappeared. A buyer asking for a grower-producer would not know whether this was an estate making wine from its own parcels or a commercial label attached to sourced wine.
The reverse happens too. A négociant with a carefully curated range may be described as an estate if its pages lean too heavily on vineyard imagery without saying what is owned, sourced, blended, or distributed. Wine writing loves landscape. Machines need roles.
A clear page does not need to give a legal lecture. It needs to say what the entity is. “Maison X is a Bordeaux négociant, selecting, blending, and selling wines from partner producers.” “Château Y is a grower-producer estate, farming its own parcels and bottling its wines under the château name.” These sentences are plain, maybe almost dry. That is their virtue.
The machine cannot preserve a distinction the public wording treats as embarrassing or too technical to state.
French precision can be lost in English softness
French wine pages often carry role signals in ordinary phrases. “Propriété familiale.” “Vigneron indépendant.” “Mise en bouteille à la propriété.” “Cave coopérative.” “Maison de négoce.” These are not decorative. They tell a trained reader where the business sits.
Then the English page is written as a hospitality text. “Discover our passion for Bordeaux wines.” “Explore our range.” “A family name rooted in tradition.” The relation between land, grapes, wine, and commerce becomes softer. That softness is not neutral. In English buyer queries, it may become the main evidence.
I see this especially when the English page tries to avoid words that feel hard to translate. Négociant is sometimes left unexplained or replaced with “wine producer.” Grower-producer becomes “wine brand.” Cooperative becomes “winery.” The result reads smoother, but it no longer teaches the answer engine the business shape.
There is also a small trap in bilingual repetition. A French page may say the estate produces wine from its parcels. An English directory may say the business “offers a selection of Bordeaux wines.” If both are true in different contexts, the pages need to explain the difference. Maybe the estate wine is one offer and the shop carries partner wines. Maybe a négociant line sits beside an estate label. Maybe the château name is used for a property and a broader commercial range. Those are manageable complexities. Hidden complexity turns into machine confusion.
I would rather see one slightly awkward English sentence than a beautiful paragraph that ducks the role. Something like: “The château’s own wines are estate-grown and estate-bottled; any partner wines are presented separately from the château label.” That sentence may never win a brochure prize. It can prevent a bad answer.
Role proof belongs near the offer
Many producers put role information on an “About” page and offer information somewhere else. The answer engine may not connect them. A wine page says “Our range.” A visit page says “taste our Bordeaux wines.” A shop says “buy the brand.” The About page quietly says “family property in Saint-Émilion.” The machine grabs the offer page because that is where the buyer’s query points.
If the buyer asks for “Bordeaux grower-producer shipping direct,” the answer may read the shop and ignore the role. If the buyer asks for “négociant Bordeaux red wine selection,” it may read the product range and over-assign the merchant role. Role proof has to sit close to the pages that answer commercial questions.
That does not mean every product card needs a paragraph of business history. It means the role should appear in the summary layer. The first lines of the wine page, visit page, direct-sales page, and public profiles should each carry the right entity type in their own context.
For a grower-producer château, the wine page might say: “These are the estate-bottled wines of Château Y, made from parcels farmed by the property in the Saint-Émilion appellation.” For a négociant, it might say: “Maison X is a Bordeaux négociant; this range brings together wines selected from partner estates and bottled or distributed under the maison’s commercial line.” Different sentences. Different shelf.
When I audit a source set, I mark role claims in the margin with a small code: land, grapes, cellar, label, seller, visit. It is old-fashioned and faintly ridiculous, but it works. If the same business appears as landowner on one surface, merchant on another, and generic brand on a third, the answer engine is not the first place the confusion happened.
Three role confusions I see again and again
The first is bottle-first confusion. The source names the bottle more clearly than the producer, so the answer defines the entity by the product listing. This is how a château becomes a brand. It is common when marketplaces write better short descriptions than the producer’s own pages.
The second is range confusion. A business offers several wines, maybe estate wines and partner wines, but the page does not separate them. The machine reads range as sourcing. A grower begins to look like a négociant, or a négociant begins to look like a producer with vineyards.
The third is hospitality confusion. A visit page describes tasting, landscape, and welcome, while leaving the commercial role offstage. The answer then calls the site a winery, estate, producer, tasting room, or wine merchant according to nearby source patterns. It may get the visit right and the business wrong.
These three are not official categories. They are working labels from my own cellar-card index. I use them because they force a better question. Not “which word did the AI choose?” but “which source pattern made that word feel safe?”
The correction should match the pattern. Bottle-first confusion needs producer-first product text. Range confusion needs clear separation between estate wines, selected wines, partner wines, and commercial labels. Hospitality confusion needs visit pages that identify the host before describing the experience.
A machine answer can only keep the grower and the négociant apart if the public source set keeps them apart under buyer pressure.
The fix is a small role sentence, repeated cleanly
The best repairs are often modest. A producer wants to rewrite the whole English site. I usually ask for the role sentence first. One sentence on the homepage. One on the wine page. One on the visit or direct-sales page. One in public profiles where editable. The wording can breathe a little, but the structure should hold.
For a château, the sentence should say whether it is a grower-producer estate, where it is, what it farms or bottles, and whether other offers are separate. For a négociant, the sentence should say that it selects, buys, blends, bottles, distributes, or sells wines from partner sources, depending on what is actually true. Do not pad it. Do not make the business sound more estate-like or more merchant-like because one sounds grander in a certain market.
There is a practical reason for this restraint. Answer engines reward usable summaries. A precise role sentence gives them a piece to quote or paraphrase. A fog of heritage language gives them permission to improvise.
I do not expect every buyer to care about the term négociant. Some will not. But the answer engine’s classification shapes which questions the business appears for. A grower mislabelled as a négociant may be missed in estate-visit answers. A négociant mislabelled as a grower may attract the wrong trust expectations. In Bordeaux, the commercial role is part of the product’s truth.
Before rewriting, read the current machine answer. Circle every word that assigns a job to the business. Then trace which source made that job easy to say. That is where the dust usually sits.
The Cellar Card
Bottle named — a château described as a Bordeaux négociant, then praised for “estate wines.”
Shelf mistake — grower-producer and merchant roles mixed inside one sentence.
Dust line — English pages say “brand” and “range,” while shop listings name bottles more clearly than the estate structure.
Relabel sentence — “Château Orme-Fictif is a grower-producer estate, farming its own Saint-Émilion parcels and bottling its château wines separately from any partner or merchant offers.”