Triple
T13645710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Historians of Arendelle |
E326095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theme park entertainment act |
C8344
|
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: theme park entertainment act Context triple: [Royal Historians of Arendelle, instanceOf, theme park entertainment act]
-
A.
theme park entertainment
Theme park entertainment encompasses the rides, shows, attractions, and interactive experiences designed to engage and delight visitors within a themed recreational environment.
-
B.
theme park show
chosen
A theme park show is a live or pre-recorded entertainment performance within a theme park, designed to engage guests through storytelling, music, special effects, and character appearances that enhance the park’s overall themed experience.
-
C.
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.
-
D.
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.
-
E.
theme park complex
A theme park complex is a large, integrated entertainment destination that combines multiple themed parks, attractions, accommodations, dining, and retail areas into a unified visitor experience.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:51 p.m.