Triple
T7853345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viognier |
E182109
|
entity |
| Predicate | usedInBlendStyle |
P2077
|
FINISHED |
| Object | co-fermented with Syrah in Côte-Rôtie |
—
|
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: co-fermented with Syrah in Côte-Rôtie | Statement: [Viognier, usedInBlendStyle, co-fermented with Syrah in Côte-Rôtie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBlendStyle Context triple: [Viognier, usedInBlendStyle, co-fermented with Syrah in Côte-Rôtie]
-
A.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
B.
typicalBlendStyle
chosen
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
C.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
D.
usesAsStyleOf
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
E.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18ed56d481909266d862e0ae152d |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:51 p.m.