Triple
T28771129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uerige brewery |
E726414
|
entity |
| Predicate | beerStyleRegion |
P165568
|
FINISHED |
| Object | Düsseldorf Altbier |
—
|
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: Düsseldorf Altbier | Statement: [Uerige brewery, beerStyleRegion, Düsseldorf Altbier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beerStyleRegion Context triple: [Uerige brewery, beerStyleRegion, Düsseldorf Altbier]
-
A.
beerStyleOrigin
Indicates the place or region where a particular beer style was originally developed or first became established.
-
B.
wineStyleOrigin
Indicates that a particular wine style originated in or is traditionally associated with a specific geographic region or place.
-
C.
wineClassificationRegion
Indicates that a wine is classified according to the geographic region where it is produced or designated.
-
D.
wineLawRegionType
Indicates the type or category of legal designation that governs wine production in a particular 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:15 a.m.