Triple
T37964979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fennville AVA |
E947114
|
entity |
| Predicate | grapeGrowing |
P17952
|
FINISHED |
| Object | cool-climate 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: cool-climate viticulture | Statement: [Fennville AVA, grapeGrowing, cool-climate viticulture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grapeGrowing Context triple: [Fennville AVA, grapeGrowing, cool-climate viticulture]
-
A.
grapePlantingShare
Indicates the proportion or share of grape planting activity attributed to or carried out by a particular entity relative to a larger whole.
-
B.
viticulturePractice
Indicates a relationship where a specific method, technique, or practice is used in the cultivation and management of grapevines.
-
C.
grapeFamily
Indicates that one entity belongs to, or is classified within, the same botanical family as grapes.
-
D.
viticulturalFocus
chosen
Indicates a focus on or specialization in viticulture, i.e., activities, practices, or interests centered on grape growing and vineyard management.
-
E.
grapeProduct
Indicates that one entity is a product derived from or made using grapes.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.