Triple
T3671335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakima Valley AVA (part) |
E77885
|
entity |
| Predicate | primaryAgriculturalUse |
P14072
|
FINISHED |
| Object | viticulture |
—
|
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: viticulture | Statement: [Yakima Valley AVA (part), primaryAgriculturalUse, viticulture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAgriculturalUse Context triple: [Yakima Valley AVA (part), primaryAgriculturalUse, viticulture]
-
A.
primaryLandUse
chosen
Indicates the main or dominant way in which a given piece of land is utilized or designated (e.g., residential, agricultural, commercial).
-
B.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
C.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
D.
primaryLivestock
Indicates that the specified livestock type is the main or most important kind of animal raised or kept by an entity.
-
E.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
- 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_69ad85e083008190b2e1b7085fe500bd |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc42de1bc819090e19dd0805f13a1 |
completed | March 8, 2026, 6:47 p.m. |
| PD | Predicate disambiguation | batch_69adb84a20288190a092e4a1b045fe3f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.