Triple
T29410563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Sand Beach (Ko Chang) |
E745882
|
entity |
| Predicate | hasNightlifeVenueType |
P43473
|
FINISHED |
| Object | bars |
—
|
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: bars | Statement: [White Sand Beach (Ko Chang), hasNightlifeVenueType, bars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightlifeVenueType Context triple: [White Sand Beach (Ko Chang), hasNightlifeVenueType, bars]
-
A.
hasNightlifeArea
Indicates that a place contains or is associated with an area characterized by nightlife activities such as bars, clubs, or evening entertainment venues.
-
B.
hasEntertainmentVenue
Indicates that an entity possesses, contains, or is associated with an entertainment venue as part of its facilities or offerings.
-
C.
offersNightlife
chosen
Indicates that a place provides opportunities for nighttime entertainment, such as bars, clubs, or evening events.
-
D.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
E.
nightlifeRole
Indicates the specific function or position an entity holds within nightlife activities, venues, or scenes.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a37dfc0819094fe426a758aa171 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:57 p.m.