Triple
T22898296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Painkiller cocktail |
E568235
|
entity |
| Predicate | drinkingEstablishmentType |
P133166
|
FINISHED |
| Object | beach bar |
—
|
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: beach bar | Statement: [Painkiller cocktail, drinkingEstablishmentType, beach bar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drinkingEstablishmentType Context triple: [Painkiller cocktail, drinkingEstablishmentType, beach bar]
-
A.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
B.
establishmentType
chosen
Indicates the specific kind or category of establishment that an entity is classified as.
-
C.
typeOfNightclub
Indicates a classification relationship where one entity specifies the particular kind or category of nightclub that another entity is.
-
D.
servesAlcohol
Indicates that an establishment or provider offers and supplies alcoholic beverages to customers or participants.
-
E.
hasRestaurantType
Indicates that an entity is associated with or classified as a particular type or category of restaurant.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801415dc8190b5de6095f1ed4ba5 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:41 p.m.