Triple
T20531309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autograph Collection Hotels |
E504072
|
entity |
| Predicate | hotelClassification |
P53265
|
FINISHED |
| Object | full-service hotels |
—
|
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: full-service hotels | Statement: [Autograph Collection Hotels, hotelClassification, full-service hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotelClassification Context triple: [Autograph Collection Hotels, hotelClassification, full-service hotels]
-
A.
hotelClass
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
B.
hotelCategory
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
-
C.
hotelTierRelativeToOtherUniversalHotels
Indicates how a hotel’s tier or quality level compares relative to other hotels within the same universal hotel system or portfolio.
-
D.
hotelBrand
Indicates that a hotel is affiliated with, operated by, or marketed under a specific hotel brand.
-
E.
hasHotelType
chosen
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
- 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_69e0b4b3a6e08190ae663701f50fab8e |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a06b923c81908ba24be6645a7c61 |
completed | April 20, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:37 a.m.