Triple
T9288175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melon de Bourgogne |
E223449
|
entity |
| Predicate | commonVinification |
P87421
|
FINISHED |
| Object | sur lie aging |
—
|
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: sur lie aging | Statement: [Melon de Bourgogne, commonVinification, sur lie aging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonVinification Context triple: [Melon de Bourgogne, commonVinification, sur lie aging]
-
A.
vinificationUse
Indicates the process or method of winemaking applied to a given wine or batch.
-
B.
commonVinificationGoal
Indicates that two or more vinification processes share the same intended winemaking objective or outcome.
-
C.
vinification
Indicates the process by which grapes (or other fruits) are transformed into wine through fermentation and related winemaking steps.
-
D.
traditionalVinification
Indicates that a wine is produced using traditional or historically established winemaking methods rather than modern or industrial techniques.
-
E.
oenologicalSignificance
Indicates the relationship in which something holds importance, relevance, or notable impact within the context of wine or winemaking.
- F. None of above. chosen
Provenance (4 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.