Triple
T2647270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee Hills AVA |
E53812
|
entity |
| Predicate | hasTerroirFeature |
P9793
|
FINISHED |
| Object | volcanic soils and cool climate |
—
|
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: volcanic soils and cool climate | Statement: [Dundee Hills AVA, hasTerroirFeature, volcanic soils and cool climate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerroirFeature Context triple: [Dundee Hills AVA, hasTerroirFeature, volcanic soils and cool climate]
-
A.
viticulturalCharacteristic
chosen
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
B.
hasVineyards
Indicates that one entity possesses, contains, or is associated with vineyards used for growing grapevines.
-
C.
wineGrapesCultivated
Indicates that certain grape varieties are grown or cultivated specifically for producing wine.
-
D.
viticulturalAreaType
Indicates the specific type or classification of a viticultural area associated with an entity.
-
E.
appellationType
Indicates the specific kind or category of name or designation applied to an entity.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd919bf2c81908feb768f3391e985 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.