Triple
T29552580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santa Clara Valley AVA |
E749813
|
entity |
| Predicate | primaryWineTypes |
P55208
|
FINISHED |
| Object | Bordeaux-style blends |
—
|
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: Bordeaux-style blends | Statement: [Santa Clara Valley AVA, primaryWineTypes, Bordeaux-style blends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWineTypes Context triple: [Santa Clara Valley AVA, primaryWineTypes, Bordeaux-style blends]
-
A.
wineVariety
Indicates the specific type or variety of wine associated with an entity.
-
B.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
C.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
D.
wineStylesAssociatedWith
chosen
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
E.
grapeVarietyType
Indicates the specific type or classification of a grape variety used or referred to in a given context.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0141fceb908190863778741bd4487d |
completed | May 11, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_6a0141a9628c819090c0b24ce052a2fb |
completed | May 11, 2026, 2:40 a.m. |
Created at: April 28, 2026, 5:13 p.m.