Triple
T19760824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palace Entertainment |
E474623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | family entertainment center operator |
C26443
|
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: family entertainment center operator Context triple: [Palace Entertainment, instanceOf, family entertainment center operator]
-
A.
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.
-
B.
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.
-
C.
home entertainment division
The home entertainment division is the organizational unit responsible for producing, acquiring, and distributing entertainment content and related products for in-home consumption across physical and digital platforms.
-
D.
leisure services operator
chosen
A leisure services operator manages and coordinates recreational facilities, programs, and activities to provide enjoyable, safe, and accessible leisure experiences for clients or the public.
-
E.
leisure and entertainment company
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:48 p.m.