Triple
T5072365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Beijing Resort |
E114309
|
entity |
| Predicate | hasHotelCategory |
P16418
|
FINISHED |
| Object | luxury 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: luxury hotels | Statement: [Universal Beijing Resort, hasHotelCategory, luxury hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHotelCategory Context triple: [Universal Beijing Resort, hasHotelCategory, luxury hotels]
-
A.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
B.
hotelCategory
chosen
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
-
C.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
D.
hotelClass
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
E.
hasHospitalityComponent
Indicates that something includes, involves, or is associated with a hospitality-related element, service, or function.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74ce140881909a2874663244c0db |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.