Triple
T8774980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Lakes of Columbia Valley AVA |
E208554
|
entity |
| Predicate | wineProductionFocus |
P26509
|
FINISHED |
| Object | still wines |
—
|
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: still wines | Statement: [Ancient Lakes of Columbia Valley AVA, wineProductionFocus, still wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineProductionFocus Context triple: [Ancient Lakes of Columbia Valley AVA, wineProductionFocus, still wines]
-
A.
viticulturalFocus
Indicates a focus on or specialization in viticulture, i.e., activities, practices, or interests centered on grape growing and vineyard management.
-
B.
producesWine
chosen
Indicates that one entity creates or manufactures wine as a product.
-
C.
wineLaw
Indicates a legal or regulatory relationship governing the production, sale, labeling, or distribution of wine.
-
D.
oenologicalSignificance
Indicates the relationship in which something holds importance, relevance, or notable impact within the context of wine or winemaking.
-
E.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
- 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_69ca835edb4481909b4aafb616dc5eb7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f30428881909de72c08972224f0 |
completed | March 31, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1aff3881908be6a9cbc9f50461 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:41 p.m.