Triple
T4322555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Côt |
E96551
|
entity |
| Predicate | typicalWineUse |
P55208
|
FINISHED |
| Object | single-varietal 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: single-varietal wines | Statement: [Côt, typicalWineUse, single-varietal wines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWineUse Context triple: [Côt, typicalWineUse, single-varietal wines]
-
A.
usesWineType
Indicates that one entity makes use of, incorporates, or is associated with a particular type or category of wine.
-
B.
typicalUseInChampagne
Indicates that something is commonly or characteristically used in the production, serving, or enjoyment of champagne.
-
C.
primaryGrapeUse
Indicates that a grape variety is primarily used for a particular purpose, such as winemaking, table consumption, or raisin production.
-
D.
wineStylesAssociatedWith
chosen
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
E.
wineStyle
Indicates the stylistic category or type of wine (such as its production style, sweetness, body, or other defining characteristics) associated with an entity.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351177eb88190b89fa49a88add5e8 |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:12 p.m.