Triple
T1093878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loews Royal Pacific Resort at Universal Orlando |
E24226
|
entity |
| Predicate | checkInExperience |
P5308
|
FINISHED |
| Object | front desk in main lobby |
—
|
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: front desk in main lobby | Statement: [Loews Royal Pacific Resort at Universal Orlando, checkInExperience, front desk in main lobby]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInExperience Context triple: [Loews Royal Pacific Resort at Universal Orlando, checkInExperience, front desk in main lobby]
-
A.
experiences
Indicates that an entity undergoes, feels, or is affected by a particular event, state, or condition.
-
B.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
-
C.
checkInTime
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
D.
isAttractionFor
Indicates that one entity serves as an attraction or point of interest specifically intended for another entity (such as a person, group, or audience).
-
E.
hasCheckInBuilding
Indicates that an entity has performed a check-in event within a specified building.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99d1e8c81909cf1178d68d38885 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b743175481908f3967e589717c55 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.