Triple
T35032906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derwent Valley wine region |
E1010825
|
entity |
| Predicate | wineSpecialty |
P124558
|
FINISHED |
| Object | cool-climate Pinot Noir |
—
|
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: cool-climate Pinot Noir | Statement: [Derwent Valley wine region, wineSpecialty, cool-climate Pinot Noir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineSpecialty Context triple: [Derwent Valley wine region, wineSpecialty, cool-climate Pinot Noir]
-
A.
wineSpeciality
chosen
Indicates that an entity (such as a person, place, or establishment) is particularly known for, focused on, or distinguished by a specific type or aspect of wine.
-
B.
wineLaw
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
C.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
D.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
E.
wineDevelopment
Indicates the process or progression of how a wine changes, matures, or evolves in character over time.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.