Triple
T16911197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlitterbahn Waterparks and Resorts |
E410197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | water park operator |
C1142
|
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: water park operator Context triple: [Schlitterbahn Waterparks and Resorts, instanceOf, water park operator]
-
A.
theme park operator
chosen
A theme park operator is an entity responsible for managing and overseeing the daily operations, attractions, staff, safety, and guest experience within a theme park.
-
B.
outdoor water park
An outdoor water park is a recreational facility featuring open-air water-based attractions such as pools, slides, splash pads, and lazy rivers designed for seasonal, weather-dependent fun and relaxation.
-
C.
indoor water park
An indoor water park is a climate-controlled recreational facility featuring water-based attractions such as pools, slides, and play areas designed for year-round use regardless of outdoor weather conditions.
-
D.
water ride
A water ride is an amusement attraction that uses water-filled channels, flumes, or pools to move riders through themed environments, often featuring splashes, drops, and soaking elements for entertainment.
-
E.
park operating entity
A park operating entity is an organization or authority responsible for managing, maintaining, and overseeing the daily operations, services, and regulations of a park or system of parks.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:30 a.m.