Triple
T9301783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easyHotel |
E223779
|
entity |
| Predicate | amenityPolicy |
P67682
|
FINISHED |
| Object | limited services |
—
|
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: limited services | Statement: [easyHotel, amenityPolicy, limited services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amenityPolicy Context triple: [easyHotel, amenityPolicy, limited services]
-
A.
venuePolicy
Indicates the rules or guidelines that govern how activities or events may be conducted at a particular venue.
-
B.
accommodationPolicy
chosen
Indicates the rules or guidelines that govern how accommodations are provided, used, or managed in a given context.
-
C.
bookingPolicy
Indicates the rules or conditions that govern how bookings or reservations can be made, modified, or canceled between parties.
-
D.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
E.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d34c4c819095a213360747c3a6 |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.