Triple
T38520946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hotel St. Moritz |
E922470
|
entity |
| Predicate | hasLuxuryRating |
P68536
|
FINISHED |
| Object | luxury hotel |
—
|
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: luxury hotel | Statement: [The Hotel St. Moritz, hasLuxuryRating, luxury hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuxuryRating Context triple: [The Hotel St. Moritz, hasLuxuryRating, luxury hotel]
-
A.
isLuxuryHotel
chosen
Indicates that a hotel is classified as a luxury establishment, typically offering high-end amenities, services, and accommodations.
-
B.
isLuxuryGood
Indicates that an item is considered a high-end, non-essential product associated with premium quality, exclusivity, or status.
-
C.
hasLuxuryPositioning
Indicates that an entity is positioned or marketed as a premium, high-end, or luxury offering relative to alternatives.
-
D.
hasLuxurySuites
Indicates that an entity provides or contains high-end, premium-quality suites as part of its accommodations or offerings.
-
E.
luxuryFeatures
Indicates that the subject possesses or is associated with high-end, premium, or upscale features beyond standard functionality.
- 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_69f76ea5f5588190bd0b28c82e975640 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.