Triple
T9324370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bouzeron AOC |
E224349
|
entity |
| Predicate | exclusiveGrapeVariety |
P975
|
FINISHED |
| Object | Aligoté |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Aligoté | Statement: [Bouzeron AOC, exclusiveGrapeVariety, Aligoté]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exclusiveGrapeVariety Context triple: [Bouzeron AOC, exclusiveGrapeVariety, Aligoté]
-
A.
grapeVarietyAllowed
Indicates that a specific grape variety is permitted or authorized for use in a given context, such as a wine, region, or product specification.
-
B.
traditionalGrapeVariety
Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
-
C.
primaryGrapeVariety
chosen
Indicates that one entity is the main or predominant grape variety used in producing the other entity (typically a wine or wine-based product).
-
D.
wineGrapesCultivated
Indicates that certain grape varieties are grown or cultivated specifically for producing wine.
-
E.
sparklingWineAllowed
Indicates that the use, serving, or presence of sparkling wine is permitted in the given context or under specified conditions.
- F. None of above.
Provenance (3 batches)
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_69ca8426d48481909596360f7791c7dd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd36f5c41c81908104c5b30e14827e |
completed | April 1, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cc7a643924819097f01144734901cf |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:38 p.m.