Triple
T31446151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiana’s Foods co-op |
E802191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theme park narrative element |
C30595
|
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: theme park narrative element Context triple: [Tiana’s Foods co-op, instanceOf, theme park narrative element]
-
A.
theme park setting
A theme park setting is a large, immersive entertainment environment organized around specific themes, featuring rides, attractions, performances, and themed areas designed to create a cohesive, fantastical experience for visitors.
-
B.
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.
-
C.
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.
-
D.
theme park attraction backstory location
chosen
A theme park attraction backstory location is the fictional or stylized place, with its own history and context, in which an attraction’s narrative is set, providing thematic justification for its design, characters, and events.
-
E.
theme park show
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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:09 p.m.