Triple
T31723406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troisième Cru Classé |
E809644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bordeaux wine classification rank |
C8003
|
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: Bordeaux wine classification rank Context triple: [Troisième Cru Classé, instanceOf, Bordeaux wine classification rank]
-
A.
Bordeaux wine classification
chosen
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.
French wine law designation
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.
-
C.
wine classification system
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.
-
D.
French wine regulation
French wine regulation is the legal and administrative framework that governs how wine is classified, produced, labeled, and marketed in France to protect quality, authenticity, and regional identity.
-
E.
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.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:19 p.m.