Triple
T33796610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aloft Hotels |
E866089
|
entity |
| Predicate | hasOnlineCheckIn |
P185249
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aloft Hotels, hasOnlineCheckIn, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnlineCheckIn Context triple: [Aloft Hotels, hasOnlineCheckIn, true]
-
A.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
B.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
-
C.
hasPassengerCheckInAccess
Indicates that an entity is permitted to perform or access passenger check-in functions for a given transport service or location.
-
D.
hasOnlineReservation
Indicates that an entity has a booking or reservation that was made or is managed through an online system.
-
E.
hasCheckOutTime
Indicates the specific time at which an entity is required or scheduled to check out or depart.
- F. None of above. chosen
Provenance (4 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69f7bbf812cc8190a16917c5daaff2df |
completed | May 3, 2026, 9:19 p.m. |
Created at: May 1, 2026, 1:46 a.m.