Triple
T35862850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arganda subzone |
E1037000
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subzone of a Denominación de Origen |
C65152
|
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: subzone of a Denominación de Origen Context triple: [Arganda subzone, instanceOf, subzone of a Denominación de Origen]
-
A.
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.
-
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.
Chianti subzone
A Chianti subzone is a geographically defined area within the broader Chianti wine region in Tuscany, each with specific terroir and regulations that give its wines distinct characteristics.
-
D.
subregion of Vinho Verde
A subregion of Vinho Verde is a geographically defined area within Portugal’s Vinho Verde wine region that has distinct climatic, soil, and cultural characteristics influencing the style and quality of its wines.
-
E.
sub-region of Champagne
A sub-region of Champagne is a geographically defined area within the broader Champagne wine region that has distinct terroir, grape-growing conditions, and stylistic characteristics influencing the wines produced there.
- F. None of above. chosen
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.