Triple
T16174044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grès de Montpellier |
E392515
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Appellation d’Origine Protégée |
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 Protégée Context triple: [Grès de Montpellier, instanceOf, Appellation d’Origine Protégée]
-
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.
Denominazione di Origine Controllata wine
A Denominazione di Origine Controllata wine is an Italian wine whose production, grape varieties, and geographic origin are strictly regulated and certified to ensure specific quality and regional 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.
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.
-
E.
brandy-producing region
A brandy-producing region is a geographically defined area known for cultivating grapes or other fruits and distilling them into brandy, often characterized by specific production methods and legal appellations.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
Created at: April 10, 2026, 5:02 a.m.