Triple
T30118217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paso Robles Highlands District AVA |
E765485
|
entity |
| Predicate | typicalVarieties |
P5973
|
FINISHED |
| Object | Syrah |
—
|
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: Syrah | Statement: [Paso Robles Highlands District AVA, typicalVarieties, Syrah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVarieties Context triple: [Paso Robles Highlands District AVA, typicalVarieties, Syrah]
-
A.
notableVarieties
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
-
B.
typicalVariety
chosen
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
C.
usesNativeVarieties
Indicates that an entity employs or incorporates locally adapted or indigenous varieties (such as plant, animal, or material types) in its activities or processes.
-
D.
numberOfPrimaryVarieties
Indicates the count of distinct primary varieties associated with a given entity.
-
E.
hasNonStandardizedVarieties
Indicates that an entity possesses forms or variants that are not governed by a uniform or officially established standard.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a036f0569cc8190a8ac7f4e07145d15 |
completed | May 12, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_6a036c42cf2481908760c7d48b9fc001 |
completed | May 12, 2026, 6:06 p.m. |
Created at: April 29, 2026, 7:12 p.m.