Triple
T27672682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palm Court |
E697700
|
entity |
| Predicate | associatedWithHotelCategory |
P16418
|
FINISHED |
| Object | luxury hotel |
—
|
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 hotel | Statement: [Palm Court, associatedWithHotelCategory, luxury hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHotelCategory Context triple: [Palm Court, associatedWithHotelCategory, luxury hotel]
-
A.
locatedInHotelCategory
Indicates that one entity is situated within, or belongs to, a specific category or classification of hotels.
-
B.
associatedHotel
Indicates that there is a relationship linking an entity to a specific hotel with which it is connected or affiliated.
-
C.
reservationCategory
Indicates the classification or type assigned to a reservation (such as its purpose, priority, or usage group) within a system.
-
D.
indicatedInHotelsBy
Indicates that something is highlighted, referenced, or made known within hotels by a particular source or agent.
-
E.
hotelCategory
chosen
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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a00512437d48190ad20324968ead5f4 |
completed | May 10, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a0050227350819099f41369c3d168be |
completed | May 10, 2026, 9:30 a.m. |
Created at: April 27, 2026, 2:42 p.m.