Triple
T35616906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pixar Place Hotel |
E1029196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Disneyland Resort hotel |
C32450
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Disneyland Resort hotel Context triple: [Pixar Place Hotel, instanceOf, Disneyland Resort hotel]
-
A.
Tokyo Disney Resort hotel
A Tokyo Disney Resort hotel is an accommodation facility located within or near Tokyo Disney Resort that offers themed lodging, dining, and services tailored to guests visiting the resort’s parks and entertainment areas.
-
B.
Disneyland Resort facility
chosen
A Disneyland Resort facility is any physical location, structure, or venue within the Disneyland Resort that supports guest experiences, operations, entertainment, lodging, dining, or services.
-
C.
Disneyland Paris hotel
A Disneyland Paris hotel is a themed accommodation located within or near the Disneyland Paris resort, offering immersive Disney experiences, park proximity, and exclusive guest benefits.
-
D.
Disney resort complex
A Disney resort complex is a large, themed vacation destination that combines multiple hotels, entertainment venues, dining, shopping, and recreational facilities centered around Disney parks and experiences.
-
E.
Disneyland Paris partner hotel
A Disneyland Paris partner hotel is an officially affiliated accommodation located near the resort that offers themed stays, convenient access, and select Disney-related benefits without being directly inside the Disney-owned hotel portfolio.
- F. None of above.
Provenance (1 batch)
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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.