Triple
T13989842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orval Abbey |
E336539
|
entity |
| Predicate | beerYeastType |
P46079
|
FINISHED |
| Object | Brettanomyces-influenced 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: Brettanomyces-influenced fermentation | Statement: [Orval Abbey, beerYeastType, Brettanomyces-influenced fermentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beerYeastType Context triple: [Orval Abbey, beerYeastType, Brettanomyces-influenced fermentation]
-
A.
yeastType
chosen
Indicates the specific kind or category of yeast associated with or used in relation to an entity.
-
B.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
C.
beerStyle
Indicates that one entity is the style or type classification of a beer associated with another entity.
-
D.
typeOfMalt
Indicates the specific kind or category of malt used or referenced in relation to another entity.
-
E.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2eb22e388190904fc87765176c91 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.