Triple
T34852797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garganega |
E1004643
|
entity |
| Predicate | typicalWineFlavors |
P149764
|
FINISHED |
| Object | stone fruit |
—
|
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: stone fruit | Statement: [Garganega, typicalWineFlavors, stone fruit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWineFlavors Context triple: [Garganega, typicalWineFlavors, stone fruit]
-
A.
wineCharacteristic
Indicates a descriptive property or quality attributed to a wine, such as its flavor, aroma, color, or style.
-
B.
notableFlavorNotes
chosen
Indicates that something is characterized by specific, distinguishable flavor notes that are especially prominent or noteworthy.
-
C.
wineStylesAssociatedWith
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
D.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
-
E.
sweetWineSuitability
Indicates the degree to which something is appropriate or recommended for pairing with or serving as a sweet 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_69f76dba76f0819090643cba102c41ec |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.