Triple
T25641571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ste. Michelle Wine Estates |
E642849
|
entity |
| Predicate | operatesWineryLocation |
P156661
|
FINISHED |
| Object | Woodinville, Washington |
—
|
NE NERFINISHED |
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: Woodinville, Washington | Statement: [Ste. Michelle Wine Estates, operatesWineryLocation, Woodinville, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesWineryLocation Context triple: [Ste. Michelle Wine Estates, operatesWineryLocation, Woodinville, Washington]
-
A.
wineryLocation
chosen
Indicates that a winery is located in or associated with a specific geographic place or region.
-
B.
hasWinemakingFacility
Indicates that an entity possesses or is associated with a facility where winemaking activities are carried out.
-
C.
hasNearbyWinery
Indicates that one entity is located close to, or in the vicinity of, a winery.
-
D.
vineyardLocation
Indicates the geographical place where a vineyard is situated or established.
-
E.
hasWinery
Indicates a relationship where a subject owns, operates, or is associated with a particular winery.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 21, 2026, 5:43 p.m.