Triple
T7541311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Harbor |
E178280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amusement park attraction area |
C22860
|
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: amusement park attraction area Context triple: [Hurricane Harbor, instanceOf, amusement park attraction area]
-
A.
amusement park attraction
An amusement park attraction is a designed entertainment feature or ride that provides guests with thrilling, enjoyable, or immersive experiences within a themed recreational setting.
-
B.
themed entertainment attraction
A themed entertainment attraction is an immersive, story-driven experience that combines environment design, technology, and performance to engage guests in a specific narrative or world.
-
C.
theme park entrance
The theme park entrance is the primary access point where guests transition from the outside world into the park, typically featuring ticketing, security, and iconic visual elements that establish the park’s identity and atmosphere.
-
D.
adventure park
An adventure park is a recreational facility offering a variety of physically engaging and often adrenaline-inducing outdoor activities, such as zip lines, climbing courses, and obstacle challenges, designed for fun, fitness, and exploration.
-
E.
theme park setting
A theme park setting is a large, immersive entertainment environment organized around specific themes, featuring rides, attractions, performances, and themed areas designed to create a cohesive, fantastical experience for visitors.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:48 p.m.