Triple
T31963396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Racha wine region |
E816105
|
entity |
| Predicate | wineAppellationProduced |
P68485
|
FINISHED |
| Object | Khvanchkara PDO |
—
|
NE NERFINISHED |
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: Khvanchkara PDO | Statement: [Racha wine region, wineAppellationProduced, Khvanchkara PDO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineAppellationProduced Context triple: [Racha wine region, wineAppellationProduced, Khvanchkara PDO]
-
A.
wineAppellation
chosen
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
B.
wineLawRegionName
Indicates that a specific name refers to the legal wine-producing region defined by wine regulations.
-
C.
wineLawRegionType
Indicates the type or category of legal designation that governs wine production in a particular region.
-
D.
wineStyleOrigin
Indicates that a particular wine style originated in or is traditionally associated with a specific geographic region or place.
-
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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2e818e4819088fc7699503d4242 |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:09 a.m.