Triple
T35351118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haew Suwat Waterfall |
E1020880
|
entity |
| Predicate | timeToVisit |
P78489
|
FINISHED |
| Object | often visited as a day trip from Bangkok |
—
|
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: often visited as a day trip from Bangkok | Statement: [Haew Suwat Waterfall, timeToVisit, often visited as a day trip from Bangkok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToVisit Context triple: [Haew Suwat Waterfall, timeToVisit, often visited as a day trip from Bangkok]
-
A.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
B.
popularTimeToVisit
chosen
Indicates the time period during which a place is most frequently visited or experiences peak visitor activity.
-
C.
visits
Indicates that one entity goes to or spends time at the location or presence of another entity.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
bestTimeOfDayToVisit
Indicates the time of day during which visiting something is considered most optimal or desirable.
- 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_69f76decd95c8190ae428f6a19d535de |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.