Triple
T27827706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutedel wine |
E703002
|
entity |
| Predicate | hasFermentationVessel |
P45199
|
FINISHED |
| Object | stainless steel tank |
—
|
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: stainless steel tank | Statement: [Gutedel wine, hasFermentationVessel, stainless steel tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFermentationVessel Context triple: [Gutedel wine, hasFermentationVessel, stainless steel tank]
-
A.
possibleFermentationVessel
Indicates that something can serve as a suitable container or environment in which fermentation may take place.
-
B.
primaryFermentationVessel
chosen
Indicates that one entity serves as the main container or vessel in which the primary fermentation process of another entity takes place.
-
C.
usesBottleFermentation
Indicates that a process or product involves carrying out fermentation inside a sealed bottle as part of its production.
-
D.
isFermentedAs
Indicates that one substance undergoes a fermentation process to become another specified product.
-
E.
mustBeFermentedBy
Indicates that one entity is required to undergo a fermentation process carried out by another specified 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 5:53 p.m.