Triple
T34569987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roter Veltliner |
E887597
|
entity |
| Predicate | wineLawRegionFocus |
P179326
|
FINISHED |
| Object | Wagram DAC (for blends and regional styles) |
—
|
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: Wagram DAC (for blends and regional styles) | Statement: [Roter Veltliner, wineLawRegionFocus, Wagram DAC (for blends and regional styles)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineLawRegionFocus Context triple: [Roter Veltliner, wineLawRegionFocus, Wagram DAC (for blends and regional styles)]
-
A.
wineLawRegionType
Indicates the type or category of legal designation that governs wine production in a particular region.
-
B.
wineLawRegionName
Indicates that a specific name refers to the legal wine-producing region defined by wine regulations.
-
C.
wineSubregion
Indicates that one region is a subregion within a larger, defined wine-producing region.
-
D.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
-
E.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
- F. None of above. chosen
Provenance (4 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7209404788190b82e108a25baa39e |
completed | May 3, 2026, 10:16 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: May 1, 2026, 2:02 a.m.