Triple
T38030799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivanta |
E948900
|
entity |
| Predicate | brandTierWithinIHCL |
P93352
|
FINISHED |
| Object | upper midscale to upscale |
—
|
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: upper midscale to upscale | Statement: [Vivanta, brandTierWithinIHCL, upper midscale to upscale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandTierWithinIHCL Context triple: [Vivanta, brandTierWithinIHCL, upper midscale to upscale]
-
A.
hotelTierRelativeToOtherUniversalHotels
Indicates how a hotel’s tier or quality level compares relative to other hotels within the same universal hotel system or portfolio.
-
B.
hotelBrand
Indicates that a hotel is affiliated with, operated by, or marketed under a specific hotel brand.
-
C.
isLuxuryHotel
Indicates that a hotel is classified as a luxury establishment, typically offering high-end amenities, services, and accommodations.
-
D.
brandLevel
chosen
Indicates the hierarchical rank or tier of a brand within a defined brand structure or classification system.
-
E.
hotelCategory
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.