Triple
T30664086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotel Breakers |
E780608
|
entity |
| Predicate | hasCheckInFunction |
P193062
|
FINISHED |
| Object | provides overnight lodging for Cedar Point guests |
—
|
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: provides overnight lodging for Cedar Point guests | Statement: [Hotel Breakers, hasCheckInFunction, provides overnight lodging for Cedar Point guests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCheckInFunction Context triple: [Hotel Breakers, hasCheckInFunction, provides overnight lodging for Cedar Point guests]
-
A.
hasCheckInFor
Indicates that an entity has an associated check-in record or event corresponding to another specified entity or context.
-
B.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
C.
hasCheckInProcedure
Indicates that there is a defined process or set of steps required for an entity to check in or be checked in.
-
D.
hasOnlineCheckIn
Indicates that an entity offers or supports the ability to check in via an online or digital platform.
-
E.
hasCheckInLocation
Indicates that an entity performs or is associated with a check-in action at a specific location.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: April 29, 2026, 8:31 p.m.