Triple
T21509660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rkatsiteli Beli |
E530682
|
entity |
| Predicate | wineDescriptor |
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: [Rkatsiteli Beli, wineDescriptor, fresh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wineDescriptor Context triple: [Rkatsiteli Beli, wineDescriptor, fresh]
-
A.
wineCharacteristic
chosen
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
B.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
C.
wineStructure
Indicates the overall sensory framework of a wine, encompassing how its components like acidity, tannin, body, and alcohol are balanced and interact.
-
D.
wineAppellation
Indicates that a wine originates from, and is classified under, a specific geographic appellation or designated wine-producing region.
-
E.
wineSpeciality
Indicates that an entity (such as a person, place, or establishment) is particularly known for, focused on, or distinguished by a specific type or aspect of wine.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea84dfbc8190a23d9a7d6eb2c2b5 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.