Triple
T32390353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalta resort infrastructure |
E827652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | resort infrastructure system |
C10034
|
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 infrastructure system Context triple: [Yalta resort infrastructure, instanceOf, resort infrastructure system]
-
A.
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.
-
B.
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.
-
C.
resort masterplan
A resort masterplan is a comprehensive conceptual layout that organizes the spatial, functional, and experiential components of a resort development, integrating architecture, landscape, infrastructure, and amenities into a cohesive vision.
-
D.
tourist infrastructure
chosen
Tourist infrastructure comprises the physical and organizational facilities, services, and systems (such as transportation, accommodations, attractions, and information centers) that support and enable tourism activities in a destination.
-
E.
ski area facility
A ski area facility is a designated location equipped with infrastructure and services that support skiing and related winter sports activities, such as lifts, trails, rentals, and lodges.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:52 a.m.