Triple
T16801700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutherford AVA |
E408370
|
entity |
| Predicate | hasTerroirDescriptor |
P42963
|
FINISHED |
| Object | Rutherford dust |
—
|
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: Rutherford dust | Statement: [Rutherford AVA, hasTerroirDescriptor, Rutherford dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerroirDescriptor Context triple: [Rutherford AVA, hasTerroirDescriptor, Rutherford dust]
-
A.
terroirDriven
Indicates that something, typically a product like wine or food, is strongly shaped or characterized by the specific environmental conditions and place where it originates.
-
B.
viticulturalCharacteristic
Indicates a relationship where a specific trait, quality, or property is attributed to viticulture or grape-growing practices.
-
C.
viticulturalFeature
chosen
Indicates a characteristic, condition, or attribute specifically related to grape growing or vineyard cultivation.
-
D.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.