Triple
T12347082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vouvray wines |
E294383
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appellation d’origine contrôlée wine |
C8005
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: appellation d’origine contrôlée wine Context triple: [Vouvray wines, instanceOf, appellation d’origine contrôlée wine]
-
A.
Appellation d’Origine Contrôlée product
An Appellation d’Origine Contrôlée product is a good—typically a food, wine, or spirit—whose name, production methods, and quality are legally protected and strictly regulated as originating from a specific geographic region in France.
-
B.
Bordeaux wine classification
Bordeaux wine classification is a hierarchical system that categorizes Bordeaux wines based on factors such as region, quality, and historical reputation, guiding consumers and producers in understanding their relative status and characteristics.
-
C.
French wine law designation
chosen
A French wine law designation is a legally defined classification that specifies the geographic origin, production methods, and quality standards for wines produced in France.
-
D.
wine quality designation
A wine quality designation is a classification label that indicates the assessed standard, origin, and production characteristics of a wine according to specific regulatory or rating criteria.
-
E.
French wine regulation
French wine regulation is the legal and administrative framework that governs how wine is classified, produced, labeled, and marketed in France to protect quality, authenticity, and regional identity.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.