Triple
T24648168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Six Senses Hotels Resorts Spas |
E610171
|
entity |
| Predicate | guestExperienceFeatures |
P57711
|
FINISHED |
| Object | local cultural experiences |
—
|
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: local cultural experiences | Statement: [Six Senses Hotels Resorts Spas, guestExperienceFeatures, local cultural experiences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestExperienceFeatures Context triple: [Six Senses Hotels Resorts Spas, guestExperienceFeatures, local cultural experiences]
-
A.
guestExperienceTheme
Indicates the overarching type or category of experience that characterizes a guest’s interaction or stay.
-
B.
fanExperienceFeature
Indicates a feature or aspect specifically designed to shape, enhance, or characterize a fan’s overall experience.
-
C.
notableReservationFeature
Indicates that there is a distinctive or noteworthy characteristic associated with a reservation.
-
D.
experienceFeature
chosen
Indicates that an entity undergoes, encounters, or makes use of a particular feature.
-
E.
amenitiesInclude
Indicates that a place or facility provides or contains specific amenities as part of its features.
- 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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 2:33 a.m.