Triple
T8008337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disneyland app |
E186420
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | official Disneyland Resort app |
C23377
|
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: official Disneyland Resort app Context triple: [Disneyland app, instanceOf, official Disneyland Resort app]
-
A.
Disneyland Resort event
A Disneyland Resort event is a scheduled, themed experience or gathering held within the Disneyland Resort that offers guests specialized entertainment, activities, or services beyond regular park operations.
-
B.
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.
-
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.
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.
-
E.
Walt Disney World Resort offering
A Walt Disney World Resort offering is any product, service, or experience—such as accommodations, theme park access, dining, entertainment, or vacation packages—provided under the Walt Disney World Resort brand to enhance guests’ visits.
- F. None of above. chosen
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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:19 p.m.