Triple
T25637558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corona Light |
E642746
|
entity |
| Predicate | hasFermentationType |
P14597
|
FINISHED |
| Object | bottom-fermented |
—
|
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-fermented | Statement: [Corona Light, hasFermentationType, bottom-fermented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFermentationType Context triple: [Corona Light, hasFermentationType, bottom-fermented]
-
A.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified entity.
-
B.
fermentationMethod
chosen
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
-
C.
coFermentationAllowed
Indicates that multiple substances are permitted to be fermented together in a single combined fermentation process.
-
D.
usesBottleFermentation
Indicates that a process or product involves carrying out fermentation inside a sealed bottle as part of its production.
-
E.
fermentationStatus
Indicates the current state or progress of a fermentation process for a given substance or batch.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 5:34 p.m.