Triple
T20243765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Clape AOC |
E498367
|
entity |
| Predicate | notableWhiteGrape |
P28269
|
FINISHED |
| Object | Bourboulenc |
—
|
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: Bourboulenc | Statement: [La Clape AOC, notableWhiteGrape, Bourboulenc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWhiteGrape Context triple: [La Clape AOC, notableWhiteGrape, Bourboulenc]
-
A.
notableWine
Indicates that a wine is recognized as significant, distinguished, or noteworthy in some context (such as quality, reputation, or historical importance).
-
B.
grapeVarietyType
Indicates the specific type or classification of a grape variety used or referred to in a given context.
-
C.
primaryGrapeVariety
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.
wineVariety
Indicates the specific type or variety of wine associated with an entity.
-
E.
traditionalGrapeVariety
chosen
Indicates that a grape variety is traditionally or historically used in a specific region, wine style, or cultural winemaking practice.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e67170aa248190922fc845d2265ae3 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.