Triple
T34535059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priorat DOQ |
E886645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Denominació d'Origen Qualificada |
C8220
|
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: Denominació d'Origen Qualificada Context triple: [Priorat DOQ, instanceOf, Denominació d'Origen Qualificada]
-
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.
subregion of Rioja DOCa
A subregion of Rioja DOCa is a geographically defined area within Spain’s Rioja Denominación de Origen Calificada that has distinct climatic, soil, and viticultural characteristics influencing the style and quality of its wines.
-
C.
Denominazione di Origine Controllata subzone
A Denominazione di Origine Controllata subzone is a geographically defined, more specific area within a broader DOC wine appellation that is subject to additional production rules and quality standards.
-
D.
wine quality designation
chosen
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.
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.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.