Triple
T5165431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The LINQ Hotel + Experience |
E116538
|
entity |
| Predicate | checkOutUntil |
P16580
|
FINISHED |
| Object | 11:00 |
—
|
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: 11:00 | Statement: [The LINQ Hotel + Experience, checkOutUntil, 11:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkOutUntil Context triple: [The LINQ Hotel + Experience, checkOutUntil, 11:00]
-
A.
hasCheckOutTime
chosen
Indicates the specific time at which an entity is required or scheduled to check out or depart.
-
B.
checkInTime
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
C.
extendsUntil
Indicates that something continues or remains in effect up to a specified point or limit in time or space.
-
D.
checkOutCategory
Indicates that an entity performs or records the action of checking out items that belong to a particular category.
-
E.
requiresCheckOut
Indicates that one entity must be formally checked out or borrowed before it can be used, accessed, or taken by another entity.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd792af4648190934cf2db523f6921 |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.