Triple
T29410572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Sand Beach (Ko Chang) |
E745882
|
entity |
| Predicate | targetTouristGroup |
P191576
|
FINISHED |
| Object | international tourists |
—
|
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: international tourists | Statement: [White Sand Beach (Ko Chang), targetTouristGroup, international tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetTouristGroup Context triple: [White Sand Beach (Ko Chang), targetTouristGroup, international tourists]
-
A.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
B.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
C.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
D.
touristAgency
Indicates that an entity is a travel or tourist agency that organizes or provides tourism-related services for another entity.
-
E.
hasTouristProfile
Indicates that an entity possesses characteristics, data, or attributes defining it as a tourist or related to tourism behavior.
- F. None of above. chosen
Provenance (4 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_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 28, 2026, 2:57 p.m.