Triple
T32780281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jurançon (moelleux) |
E838335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appellation d’origine contrôlée wine style |
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 style Context triple: [Jurançon (moelleux), instanceOf, appellation d’origine contrôlée wine style]
-
A.
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.
-
B.
regional wine style characteristic
A regional wine style characteristic is a defining sensory or production trait—such as flavor profile, aroma, structure, or winemaking technique—that consistently distinguishes wines from a specific geographic area.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:14 a.m.