Triple
T22748622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatr im. Wojciecha Bogusławskiego w Kaliszu |
E562627
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | instytucja kultury |
C84
|
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: instytucja kultury Context triple: [Teatr im. Wojciecha Bogusławskiego w Kaliszu, instanceOf, instytucja kultury]
-
A.
cultural institution
chosen
A cultural institution is an organized establishment, such as a museum, library, theater, or gallery, dedicated to preserving, interpreting, and promoting the arts, heritage, and shared cultural expressions of a community or society.
-
B.
cultural office
A cultural office is an organizational unit or agency dedicated to promoting, managing, and supporting cultural activities, policies, and initiatives within a community, institution, or region.
-
C.
cultural policy council
A cultural policy council is a formal advisory or decision-making body that develops, guides, and evaluates strategies, regulations, and funding priorities for a community’s cultural life and creative sectors.
-
D.
collection of cultural facilities
A collection of cultural facilities is an organized grouping of venues such as museums, theaters, galleries, and libraries that together provide spaces for cultural expression, preservation, and engagement.
-
E.
cultural institution program
A cultural institution program is a structured set of activities, events, or initiatives designed by a cultural organization to engage audiences, interpret and present cultural content, and fulfill its educational, artistic, or social mission.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:24 p.m.