Triple
T12676713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsolikouri |
E302831
|
entity |
| Predicate | associatedWithCountryWineTradition |
P105586
|
FINISHED |
| Object | Georgian wine |
—
|
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: Georgian wine | Statement: [Tsolikouri, associatedWithCountryWineTradition, Georgian wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCountryWineTradition Context triple: [Tsolikouri, associatedWithCountryWineTradition, Georgian wine]
-
A.
nationalWineTradition
Indicates that a country or region has an established cultural and historical practice of producing, consuming, and valuing wine.
-
B.
notableWineRegionCountry
Indicates that a country is recognized as a notable or significant wine-producing region.
-
C.
hasWineMakingTradition
Indicates that a place or group has an established, culturally recognized history and practice of producing wine.
-
D.
wineCountry
Indicates that a location is recognized as a region where wine is produced, typically known for its vineyards and wineries.
-
E.
wineStyleOrigin
chosen
Indicates that a particular wine style originated in or is traditionally associated with a specific geographic region or place.
- 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961b0d9c88190a05d6cbcb7a1642d |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.