Triple
T36445967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josef Groll |
E897870
|
entity |
| Predicate | usedBrewingMethod |
P194393
|
FINISHED |
| Object | bottom fermentation |
—
|
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: bottom fermentation | Statement: [Josef Groll, usedBrewingMethod, bottom fermentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBrewingMethod Context triple: [Josef Groll, usedBrewingMethod, bottom fermentation]
-
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.
coffeeProcessingMethods
Indicates the methods or techniques used to transform raw coffee cherries or beans into a consumable coffee product.
-
D.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
E.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:10 p.m.