Triple
T10116310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyatt House Washington D.C. / The Wharf |
E218366
|
entity |
| Predicate | hasCheckOut |
P16580
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Hyatt House Washington D.C. / The Wharf, hasCheckOut, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckOut Context triple: [Hyatt House Washington D.C. / The Wharf, hasCheckOut, morning]
-
A.
hasCheckOutTime
chosen
Indicates the specific time at which an entity is required or scheduled to check out or depart.
-
B.
requiresCheckOut
Indicates that one entity must be formally checked out or borrowed before it can be used, accessed, or taken by another entity.
-
C.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
D.
hasReservationStatus
Indicates that an entity is associated with a specific reservation and the current status or state of that reservation (e.g., pending, confirmed, canceled).
-
E.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd162fac0819084c74947c1f6688e |
completed | April 2, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.