Triple
T19359954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deluxe Resort Hotels |
E484250
|
entity |
| Predicate | offersAmenityLevel |
P9546
|
FINISHED |
| Object | upscale amenities |
—
|
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: upscale amenities | Statement: [Deluxe Resort Hotels, offersAmenityLevel, upscale amenities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAmenityLevel Context triple: [Deluxe Resort Hotels, offersAmenityLevel, upscale amenities]
-
A.
amenityLevel
chosen
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
B.
amenitiesInclude
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
C.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
D.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
E.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6190b343c81909734ba776fd196dc |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.