Triple
T27650575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omni Rancho Las Palmas Resort & Spa |
E696841
|
entity |
| Predicate | isLuxury |
P68536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Omni Rancho Las Palmas Resort & Spa, isLuxury, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLuxury Context triple: [Omni Rancho Las Palmas Resort & Spa, isLuxury, true]
-
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.
hasLuxuryBrands
Indicates that an entity possesses, offers, or is associated with one or more luxury brands.
-
D.
luxurySegment
Indicates that the associated entity belongs to, targets, or is positioned within the luxury or premium market segment.
-
E.
luxuryOrientation
Indicates a tendency or strategic focus toward luxury, premium, or high-end qualities, experiences, or positioning.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f631d4dfbc819094c0e200e214ec08 |
completed | May 2, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 2:31 p.m.