Triple
T6171146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anderson Valley Pinot Noir Festival |
E137698
|
entity |
| Predicate | mainWineType |
P52137
|
FINISHED |
| Object | Pinot Noir |
—
|
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: Pinot Noir | Statement: [Anderson Valley Pinot Noir Festival, mainWineType, Pinot Noir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWineType Context triple: [Anderson Valley Pinot Noir Festival, mainWineType, Pinot Noir]
-
A.
wineCategory
Indicates the classification or type of wine that an entity (such as a specific wine) belongs to.
-
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.
usesWineType
chosen
Indicates that one entity makes use of, incorporates, or is associated with a particular type or category of wine.
-
D.
wineStylesAssociatedWith
Indicates a relationship where certain wine styles are linked or connected to a particular entity, such as a region, grape, producer, or product.
-
E.
wineClassificationSystem
Indicates a system or scheme used to categorize and organize wines based on defined criteria such as origin, style, or quality.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d910c3c8190ae6af548259295ff |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.