Triple
T6169784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McWilliam’s Wines (Hanwood near Griffith) |
E137662
|
entity |
| Predicate | hasTastingExperience |
P22539
|
FINISHED |
| Object | on-site wine tastings |
—
|
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: on-site wine tastings | Statement: [McWilliam’s Wines (Hanwood near Griffith), hasTastingExperience, on-site wine tastings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTastingExperience Context triple: [McWilliam’s Wines (Hanwood near Griffith), hasTastingExperience, on-site wine tastings]
-
A.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
B.
hasTastingRoom
chosen
Indicates that an establishment provides a dedicated space where visitors can sample or taste its products on-site.
-
C.
hasSpice
Indicates that one entity contains, includes, or is characterized by a particular spice or set of spices.
-
D.
hasBitternessLevel
Indicates that an entity is associated with a specific degree or intensity of bitterness.
-
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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d8f97708190bebbc49c4a56c8a5 |
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.