Triple
T25833228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaweng Beach |
E650720
|
entity |
| Predicate | hasTimeOfPeakTourism |
P78489
|
FINISHED |
| Object | dry season |
—
|
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: dry season | Statement: [Chaweng Beach, hasTimeOfPeakTourism, dry season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOfPeakTourism Context triple: [Chaweng Beach, hasTimeOfPeakTourism, dry season]
-
A.
hasPeakVisitationSeason
Indicates that an entity experiences its highest or most concentrated level of visitation during a specific season or time period.
-
B.
popularTimeToVisit
chosen
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
-
C.
hasTouristPopularity
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
D.
hasTouristVisits
Indicates that one entity experiences or records visits from tourists to another entity.
-
E.
hasSeasonalRidershipPeak
Indicates that the ridership of an entity (such as a service or route) reaches its highest levels during specific seasons or times of the year.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 7:39 a.m.