Triple
T17790059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Drézéry |
E444133
|
entity |
| Predicate | wineRegionTradition |
P26577
|
FINISHED |
| Object | historic Languedoc wine culture |
—
|
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: historic Languedoc wine culture | Statement: [Saint-Drézéry, wineRegionTradition, historic Languedoc wine culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineRegionTradition Context triple: [Saint-Drézéry, wineRegionTradition, historic Languedoc wine culture]
-
A.
nationalWineTradition
chosen
Indicates that a country or region has an established cultural and historical practice of producing, consuming, and valuing wine.
-
B.
wineRegionSpecialization
Indicates a relationship where a wine-producing region is characterized by or particularly known for specializing in a specific type or style of wine.
-
C.
wineRegionCategory
Indicates a classification relationship where a wine region is assigned to a specific category or type of wine-producing area.
-
D.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
-
E.
wineSubregion
Indicates that one region is a subregion within a larger, defined wine-producing region.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.