Triple
T26816458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Squirt Garden |
E675131
|
entity |
| Predicate | associatedHotel |
P200198
|
FINISHED |
| Object | Disney Explorers Lodge |
—
|
NE NERFINISHED |
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: Disney Explorers Lodge | Statement: [Little Squirt Garden, associatedHotel, Disney Explorers Lodge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedHotel Context triple: [Little Squirt Garden, associatedHotel, Disney Explorers Lodge]
-
A.
associatedResort
Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
-
B.
officialHotelOf
Indicates that one entity serves as the designated or formally recognized hotel associated with another entity, such as an event, organization, or venue.
-
C.
hasPartnerHotel
Indicates that one hotel has an established partnership or affiliation relationship with another hotel.
-
D.
hotelOperator
Indicates that an entity operates, manages, or runs a hotel as its responsible service provider or business owner.
-
E.
hotelBrand
Indicates that a hotel is affiliated with, operated by, or marketed under a specific hotel brand.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69ff7ae4bc948190a4cd21a60d091977 |
completed | May 9, 2026, 6:20 p.m. |
Created at: April 27, 2026, 4:52 a.m.