Triple
T20162230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhône AOC system |
E491737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | French appellation d’origine contrôlée framework |
C7786
|
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: French appellation d’origine contrôlée framework Context triple: [Rhône AOC system, instanceOf, French appellation d’origine contrôlée framework]
-
A.
French wine law designation
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.
-
B.
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.
-
C.
French wine regulation
chosen
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.
-
D.
Swiss AOC
Swiss AOC is a certification system that designates and protects the geographical origin and traditional production methods of Swiss agricultural products, particularly wines and cheeses.
-
E.
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.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
Created at: April 11, 2026, 11:34 p.m.