Triple
T16246083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cinsault |
E394373
|
entity |
| Predicate | isOftenVinifiedAs |
P77755
|
FINISHED |
| Object | single-varietal wine |
—
|
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: single-varietal wine | Statement: [Cinsault, isOftenVinifiedAs, single-varietal wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenVinifiedAs Context triple: [Cinsault, isOftenVinifiedAs, single-varietal wine]
-
A.
commonVinification
Indicates that two wines share the same or very similar vinification (winemaking) process.
-
B.
vinification
Indicates the process by which grapes (or other fruits) are transformed into wine through fermentation and related winemaking steps.
-
C.
vinificationUse
chosen
Indicates the process or method of winemaking applied to a given wine or batch.
-
D.
traditionalVinification
Indicates that a wine is produced using traditional or historically established winemaking methods rather than modern or industrial techniques.
-
E.
commonVinificationGoal
Indicates that two or more vinification processes share the same intended winemaking objective or outcome.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24561d250819096f709ea8751fcb9 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.