Triple
T20214106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grant Hotel (San Diego) |
E493568
|
entity |
| Predicate | hasLuxuryLevel |
P68536
|
FINISHED |
| Object | luxury |
—
|
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 | Statement: [Grant Hotel (San Diego), hasLuxuryLevel, luxury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLuxuryLevel Context triple: [Grant Hotel (San Diego), hasLuxuryLevel, luxury]
-
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.
hasLuxurySuites
Indicates that an entity provides or contains high-end, premium-quality suites as part of its accommodations or offerings.
-
D.
hasLuxuryBrands
Indicates that an entity possesses, offers, or is associated with one or more luxury brands.
-
E.
hasLoungeCar
Indicates that something includes or is equipped with a lounge car as part of its composition or configuration.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed8101081908e53a8bde48624b1 |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.