Triple
T18948215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahr wine region |
E463570
|
entity |
| Predicate | wineLawRegionType |
P133907
|
FINISHED |
| Object | Anbaugebiet |
—
|
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: Anbaugebiet | Statement: [Ahr wine region, wineLawRegionType, Anbaugebiet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineLawRegionType Context triple: [Ahr wine region, wineLawRegionType, Anbaugebiet]
-
A.
wineLawRegionName
Indicates that a specific name refers to the legal wine-producing region defined by wine regulations.
-
B.
wineClassificationRegion
Indicates that a wine is classified according to the geographic region where it is produced or designated.
-
C.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
D.
wineSubregion
Indicates that one region is a subregion within a larger, defined wine-producing region.
-
E.
wineRegion
Indicates the geographical region or area where a particular wine is produced or originates.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.