Triple
T16779079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andechser Weissbier Hell |
E407808
|
entity |
| Predicate | recommendedGlassware |
P104024
|
FINISHED |
| Object | Weissbier glass |
—
|
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: Weissbier glass | Statement: [Andechser Weissbier Hell, recommendedGlassware, Weissbier glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedGlassware Context triple: [Andechser Weissbier Hell, recommendedGlassware, Weissbier glass]
-
A.
glassType
chosen
Indicates the specific kind or category of glass associated with or used by an entity.
-
B.
wineServingSuggestion
Indicates the recommended way or context in which a particular wine is best served or enjoyed.
-
C.
wineComponent
Indicates that one entity is a constituent ingredient or part of a wine represented by the other entity.
-
D.
traditionalWineChoice
Indicates that an entity selects or prefers a wine option that aligns with customary or historically established pairing or serving practices.
-
E.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
- 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_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. |
Created at: April 10, 2026, 5:22 a.m.