Triple
T3352325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usakhelauri |
E70523
|
entity |
| Predicate | fermentationType |
P14597
|
FINISHED |
| Object | natural 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: natural fermentation | Statement: [Usakhelauri, fermentationType, natural fermentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fermentationType Context triple: [Usakhelauri, fermentationType, natural fermentation]
-
A.
fermentationMethod
chosen
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
-
B.
fermentationBase
Indicates that one entity serves as the primary substrate or starting material used in the fermentation process that produces or transforms the other entity.
-
C.
fermentedFood
Indicates that one entity is a food item that has been produced or altered through a fermentation process involving microorganisms.
-
D.
possibleFermentationVessel
Indicates that something can serve as a suitable container or environment in which fermentation may take place.
-
E.
yeastType
Indicates the specific kind or category of yeast associated with or used in relation to an entity.
- 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_69ad85a4ef7c8190a29e2bbd6fa454e4 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb221a7d8819086cd0f826eca0fe8 |
completed | March 8, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69ada42fbe7c8190b9f185b5ab985f17 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.