Triple
T32601193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Disney Resort Good Neighbor Hotels |
E833378
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tokyo Disney Resort affiliated hotels category |
C23100
|
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: Tokyo Disney Resort affiliated hotels category Context triple: [Tokyo Disney Resort Good Neighbor Hotels, instanceOf, Tokyo Disney Resort affiliated hotels category]
-
A.
Tokyo Disney Resort hotel
chosen
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 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.
-
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 Resort facility
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.
-
E.
Tokyo Disney Resort ticket
A Tokyo Disney Resort ticket is a time-bound admission pass that grants a guest access to specified parks, dates, and attractions within Tokyo Disney Resort under defined usage conditions.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.