Triple
T32767276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalay Bay–Luxor–Excalibur resort corridor |
E837936
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | resort corridor |
C60935
|
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: resort corridor Context triple: [Mandalay Bay–Luxor–Excalibur resort corridor, instanceOf, resort corridor]
-
A.
camping corridor
A camping corridor is a designated linear area within a campground or natural setting that provides organized access and space for campsites, pathways, and shared facilities while minimizing environmental impact.
-
B.
institutional corridor
An institutional corridor is a long, functional passageway within a formal facility (such as a school, hospital, or government building) that connects rooms and departments while regulating movement and access.
-
C.
resort
A resort is a commercial establishment that provides lodging, dining, recreation, and leisure amenities in a single destination designed for relaxation and vacation experiences.
-
D.
resort section
A resort section is a designated area within a resort property that groups together specific accommodations, amenities, or themed experiences to provide a cohesive and targeted guest experience.
-
E.
ceremonial corridor
A ceremonial corridor is a formal, often architecturally embellished passageway designed to frame and elevate processions, rituals, or symbolic movement through a space.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:13 a.m.