Triple
T34818195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Échelle des Crus |
E1003694
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Champagne vineyard classification system |
C8004
|
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: Champagne vineyard classification system Context triple: [Échelle des Crus, instanceOf, Champagne vineyard classification system]
-
A.
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.
-
B.
wine classification system
chosen
A wine classification system is a structured framework that categorizes wines based on attributes such as grape variety, region, vintage, production methods, and quality level to support consistent identification, comparison, and selection.
-
C.
Champagne sweetness level
Champagne sweetness level is a classification of Champagne based on its residual sugar content, ranging from very dry (Brut Nature) to very sweet (Doux).
-
D.
Burgundy Premier Cru climat
A Burgundy Premier Cru climat is a precisely defined vineyard site recognized for its superior terroir and quality potential, producing wines ranked just below Grand Cru within Burgundy’s classification hierarchy.
-
E.
Count of Champagne
The Count of Champagne was a powerful medieval French noble title whose holders ruled the prosperous and strategically important County of Champagne, playing key roles in European politics, trade, and crusading.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 4 p.m.