Triple
T28929465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Victoria wine zone |
E733740
|
entity |
| Predicate | notableWhiteVariety |
P59038
|
FINISHED |
| Object | Riesling |
—
|
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: Riesling | Statement: [Western Victoria wine zone, notableWhiteVariety, Riesling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWhiteVariety Context triple: [Western Victoria wine zone, notableWhiteVariety, Riesling]
-
A.
primaryWhiteVariety
Indicates that one entity is the primary white (light-skinned or white-colored) variety or form of another entity.
-
B.
notableVarieties
chosen
Indicates that there are specific, distinguished types or versions associated with an entity that are recognized as notable.
-
C.
notableVariation
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
D.
notableColor
Indicates that an entity is characteristically or prominently associated with a particular color.
-
E.
isPrimaryVarietyOf
Indicates that one variety is the main or principal form of another related variety or 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
Created at: April 28, 2026, 8:26 a.m.