Triple
T14923224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hastings Seafood and Wine Festival |
E371565
|
entity |
| Predicate | typeOfDrinkServed |
P68535
|
FINISHED |
| Object | wine |
—
|
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: wine | Statement: [Hastings Seafood and Wine Festival, typeOfDrinkServed, wine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDrinkServed Context triple: [Hastings Seafood and Wine Festival, typeOfDrinkServed, wine]
-
A.
drinks
Indicates that one entity consumes a liquid substance, typically by ingesting it through the mouth.
-
B.
beverageSubcategory
chosen
Indicates a more specific classification within a broader beverage category, defining the subtype or subcategory of a drink.
-
C.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
D.
hasBeverageCategory
Indicates that an entity is associated with or classified under a particular beverage category.
-
E.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6323f8c8190af02d06352d459c3 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:34 a.m.