Triple
T19499550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Memorial Court theatre and leisure centre |
E487865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theatre and leisure centre |
C25877
|
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: theatre and leisure centre Context triple: [Memorial Court theatre and leisure centre, instanceOf, theatre and leisure centre]
-
A.
community theatre venue
A community theatre venue is a local performance space that hosts amateur and semi-professional theatrical productions, fostering artistic expression, cultural engagement, and social connection within its surrounding community.
-
B.
entertainment facility
chosen
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.
-
C.
children’s theatre venue
A children’s theatre venue is a performance space specifically designed and programmed to present live, age-appropriate theatrical productions and related activities for young audiences and their families.
-
D.
performing and visual arts center
A performing and visual arts center is a dedicated facility that hosts, presents, and supports a variety of live performances and visual art exhibitions, often including theaters, galleries, studios, and related educational spaces.
-
E.
group of theatres
A group of theatres is an organized collection of multiple theatre venues, typically managed under a single ownership or brand for coordinated programming, operations, and marketing.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:40 p.m.