Triple
T16716975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andechser Doppelbock Dunkel |
E406247
|
entity |
| Predicate | beerSubcategory |
P52234
|
FINISHED |
| Object | strong dark lager |
—
|
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: strong dark lager | Statement: [Andechser Doppelbock Dunkel, beerSubcategory, strong dark lager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beerSubcategory Context triple: [Andechser Doppelbock Dunkel, beerSubcategory, strong dark lager]
-
A.
beerStyle
chosen
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
B.
beerColor
Indicates the color characteristic associated with a particular beer.
-
C.
drinkFamily
Indicates a familial or close relational connection between two entities centered around drinking-related activities or contexts.
-
D.
alcoholType
Indicates the specific kind or category of alcohol associated with an entity (e.g., beer, wine, spirits).
-
E.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38656b66081909f2c2a8971c45aee |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.