Triple
T10662491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelico |
E251260
|
entity |
| Predicate | commonWineUse |
P52137
|
FINISHED |
| Object | blended white wines |
—
|
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: blended white wines | Statement: [Angelico, commonWineUse, blended white wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonWineUse Context triple: [Angelico, commonWineUse, blended white wines]
-
A.
usesWineType
chosen
Indicates that one entity makes use of, incorporates, or is associated with a particular type or category of wine.
-
B.
primaryGrapeUse
Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
-
C.
traditionalWineChoice
Indicates that an entity selects or prefers a wine option that aligns with customary or historically established pairing or serving practices.
-
D.
typicalUseInChampagne
Indicates that something is commonly or characteristically used in the production, serving, or enjoyment of champagne.
-
E.
vinificationUse
Indicates the process or method of winemaking applied to a given wine or batch.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e018d1e881909b8e62682104e842 |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.