Triple
T16717042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andechser Export Dunkel |
E406249
|
entity |
| Predicate | isBavarianBeer |
P124350
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Andechser Export Dunkel, isBavarianBeer, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBavarianBeer Context triple: [Andechser Export Dunkel, isBavarianBeer, true]
-
A.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
B.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
C.
localBeerTradition
Indicates that a place has an established, culturally recognized practice of brewing, serving, or consuming beer that is distinctive to that locality.
-
D.
isMixedBeer
Indicates that a beer is composed by mixing two or more different beers together.
-
E.
isMassMarketBeer
Indicates that a beer is produced and distributed on a large commercial scale for broad, mainstream consumer markets.
- 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_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. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.