Triple
T30498949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MINILAND |
E776083
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LEGO attraction |
C20177
|
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: LEGO attraction Context triple: [MINILAND, instanceOf, LEGO attraction]
-
A.
LEGO retail experience
The LEGO retail experience is an immersive, hands-on shopping environment where customers of all ages can explore, build, customize, and purchase LEGO products through interactive displays, play zones, and personalized services.
-
B.
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.
-
C.
themed entertainment attraction
chosen
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.
-
D.
Universal Parks & Resorts attraction
A Universal Parks & Resorts attraction is an entertainment experience—such as a ride, show, or interactive area—designed and operated by Universal within its theme parks to immerse guests in stories, characters, and worlds from its intellectual properties and partner franchises.
-
E.
theme park facility
A theme park facility is a specialized venue or structure within a theme park designed to support attractions, entertainment, guest services, or operations, such as rides, theaters, restaurants, shops, or maintenance areas.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:14 p.m.