Triple
T2622345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding Nemo: The Big Blue... and Beyond! |
E59036
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | live entertainment attraction |
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: live entertainment attraction Context triple: [Finding Nemo: The Big Blue... and Beyond!, instanceOf, live entertainment attraction]
-
A.
entertainment complex
An entertainment complex is a large, multi-purpose facility that combines various leisure, recreational, and cultural attractions—such as cinemas, theaters, restaurants, gaming areas, and event spaces—within a single integrated venue.
-
B.
entertainment district
An entertainment district is a designated urban area concentrated with venues such as theaters, bars, clubs, restaurants, and other leisure attractions that cater to nightlife and recreational activities.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:50 p.m.