Triple
T32856415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jurançon Sec |
E840386
|
entity |
| Predicate | typicalWinemaking |
P77755
|
FINISHED |
| Object | temperature-controlled 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: temperature-controlled fermentation | Statement: [Jurançon Sec, typicalWinemaking, temperature-controlled fermentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWinemaking Context triple: [Jurançon Sec, typicalWinemaking, temperature-controlled fermentation]
-
A.
commonVinification
Indicates that two wines share the same or very similar vinification (winemaking) process.
-
B.
oenologicalPractice
Indicates a relationship where an entity is involved in, applies, or is characterized by a specific winemaking or wine-handling practice.
-
C.
traditionalVinification
Indicates that a wine is produced using traditional or historically established winemaking methods rather than modern or industrial techniques.
-
D.
vinificationUse
chosen
Indicates the process or method of winemaking applied to a given wine or batch.
-
E.
vinification
Indicates the process by which grapes (or other fruits) are transformed into wine through fermentation and related winemaking steps.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:17 a.m.