Triple
T12693188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leading Hotels of the World |
E303258
|
entity |
| Predicate | hotelTypeRepresented |
P53265
|
FINISHED |
| Object | city 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: city hotels | Statement: [Leading Hotels of the World, hotelTypeRepresented, city hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotelTypeRepresented Context triple: [Leading Hotels of the World, hotelTypeRepresented, city hotels]
-
A.
hasHotelType
chosen
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
B.
hotelCategory
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
-
C.
hotelClass
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
D.
hotelBrand
Indicates that a hotel is affiliated with, operated by, or marketed under a specific hotel brand.
-
E.
hostsDepositType
Indicates that an entity (such as an account, platform, or institution) supports or accommodates a particular type or category of deposit.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.