Triple
T33654442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Works |
E862184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community-based theater program |
C21870
|
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: community-based theater program Context triple: [Public Works, instanceOf, community-based theater program]
-
A.
community-based program
chosen
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
-
B.
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.
-
C.
student-run theatre
A student-run theatre is a performance organization entirely managed and operated by students, who oversee all aspects of production from selecting plays and directing to acting, designing, and handling technical and administrative tasks.
-
D.
municipal theater company
A municipal theater company is a publicly funded performing arts organization operated or supported by a local government to produce theatrical works and cultural programming for the community.
-
E.
theater workshop
A theater workshop is a structured, collaborative learning environment where participants explore and develop performance skills through exercises, improvisations, and guided practice.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:42 a.m.