Triple
T13972567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbling |
E336100
|
entity |
| Predicate | wineFlavorProfile |
P16142
|
FINISHED |
| Object | fresh |
—
|
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: fresh | Statement: [Elbling, wineFlavorProfile, fresh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineFlavorProfile Context triple: [Elbling, wineFlavorProfile, fresh]
-
A.
wineCharacteristic
chosen
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
B.
wineStyleContribution
Indicates how much a given factor or component influences or shapes the overall style or character of a wine.
-
C.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
D.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
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_69d81c61f3508190aaf2ca0dc0002c59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e8eae40819080dd4bd25c73b6d6 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.