Triple
T16779077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andechser Weissbier Hell |
E407808
|
entity |
| Predicate | brewedAccordingTo |
P124593
|
FINISHED |
| Object | Bavarian brewing tradition |
—
|
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: Bavarian brewing tradition | Statement: [Andechser Weissbier Hell, brewedAccordingTo, Bavarian brewing tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brewedAccordingTo Context triple: [Andechser Weissbier Hell, brewedAccordingTo, Bavarian brewing tradition]
-
A.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
B.
coffeeOrganization
Indicates a relationship where an organization is involved with coffee, such as producing, distributing, selling, or promoting it.
-
C.
coffeeProfile
Indicates the characteristic flavor, aroma, and strength attributes that define a particular coffee.
-
D.
coffeeDesignation
Indicates that one entity is designated or classified as a particular type, role, or category of coffee in relation to another entity.
-
E.
beverageSubcategory
Indicates a more specific classification within a broader beverage category, defining the subtype or subcategory of a drink.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b21401b881909bbbc7382e851a90 |
completed | April 18, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.