Triple
T4635626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taj Dubai |
E101521
|
entity |
| Predicate | hasCheckInPolicy |
P30190
|
FINISHED |
| Object | standard hotel check-in and check-out times |
—
|
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: standard hotel check-in and check-out times | Statement: [Taj Dubai, hasCheckInPolicy, standard hotel check-in and check-out times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInPolicy Context triple: [Taj Dubai, hasCheckInPolicy, standard hotel check-in and check-out times]
-
A.
checkInPolicy
chosen
Indicates the rules or conditions governing when and how an entity is allowed to check in (e.g., arrive, register, or log presence) in relation to another entity or context.
-
B.
hasReservationPolicy
Indicates that an entity specifies or is governed by a particular policy regarding how reservations are made, managed, or honored.
-
C.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
D.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
E.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a60a66c8190b76f3d3a7da1df55 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.