Triple
T30197423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacherenc-du-Vic-Bilh |
E767672
|
entity |
| Predicate | sweetWineStyle |
P2082
|
FINISHED |
| Object | late-harvest 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: late-harvest wine | Statement: [Pacherenc-du-Vic-Bilh, sweetWineStyle, late-harvest wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sweetWineStyle Context triple: [Pacherenc-du-Vic-Bilh, sweetWineStyle, late-harvest wine]
-
A.
wineStyle
chosen
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
B.
sweetWineSuitability
Indicates the degree to which something is appropriate or recommended for pairing with or serving as a sweet wine.
-
C.
wineStyleContribution
Indicates how much a given factor or component influences or shapes the overall style or character of a wine.
-
D.
sparklingWineSweetnessRange
Indicates the range of sweetness levels that a sparkling wine can have or is classified within.
-
E.
wineStylesAssociatedWith
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:30 p.m.