Triple
T10039016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Faisaliah Hotel |
E205246
|
entity |
| Predicate | hasCheckInService |
P22278
|
FINISHED |
| Object | 24-hour front desk |
—
|
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: 24-hour front desk | Statement: [Al Faisaliah Hotel, hasCheckInService, 24-hour front desk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInService Context triple: [Al Faisaliah Hotel, hasCheckInService, 24-hour front desk]
-
A.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
B.
hasCheckInCategory
Indicates that an entity is associated with a specific category or type of check-in event.
-
C.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
hasVisitorServices
chosen
Indicates that an entity provides services or facilities specifically intended for visitors or guests.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee04afc8190904704d66e23a432 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.