Triple
T26331485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savagnin |
E662395
|
entity |
| Predicate | associatedWithWinemakingTechnique |
P137849
|
FINISHED |
| Object | flor 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: flor aging | Statement: [Savagnin, associatedWithWinemakingTechnique, flor aging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWinemakingTechnique Context triple: [Savagnin, associatedWithWinemakingTechnique, flor aging]
-
A.
vinificationUse
Indicates the process or method of winemaking applied to a given wine or batch.
-
B.
hasWinemakingOption
Indicates that an entity offers or includes a particular method, feature, or configuration related to winemaking.
-
C.
oenologicalPractice
chosen
Indicates a relationship where an entity is involved in, applies, or is characterized by a specific winemaking or wine-handling practice.
-
D.
grapeVarietyWorkedWith
Indicates that an entity (typically a person, organization, or producer) has worked with or handled a particular grape variety in some professional or practical capacity.
-
E.
commonVinification
Indicates that two wines share the same or very similar vinification (winemaking) process.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: April 26, 2026, 10:34 p.m.