Triple
T12050380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEGOLAND Discovery Centres |
E286899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indoor family entertainment attraction brand |
C12210
|
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: indoor family entertainment attraction brand Context triple: [LEGOLAND Discovery Centres, instanceOf, indoor family entertainment attraction brand]
-
A.
indoor theme park
chosen
An indoor theme park is a fully enclosed entertainment complex featuring climate-controlled rides, attractions, games, and themed environments designed for year-round enjoyment regardless of weather conditions.
-
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.
family entertainment venue
A family entertainment venue is a place designed to provide a variety of safe, fun, and age-appropriate recreational activities and attractions for children and adults to enjoy together.
-
D.
themed entertainment space
A themed entertainment space is a carefully designed environment that immerses guests in a specific story, setting, or concept through coordinated architecture, decor, technology, and interactive experiences.
-
E.
entertainment facility
An entertainment facility is a venue designed and equipped to provide recreational, cultural, or leisure activities to individuals or groups, such as theaters, amusement parks, sports arenas, or gaming centers.
- 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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.