Triple
T33927548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchor Brewing Company |
E869793
|
entity |
| Predicate | hasBrewingStyle |
P52234
|
FINISHED |
| Object | steam beer |
—
|
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: steam beer | Statement: [Anchor Brewing Company, hasBrewingStyle, steam beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrewingStyle Context triple: [Anchor Brewing Company, hasBrewingStyle, steam beer]
-
A.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
B.
brewedUsing
Indicates that one entity was produced or prepared by using another entity as an ingredient, material, or component in a brewing process.
-
C.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
D.
beerStyle
chosen
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:49 a.m.