Triple
T17452829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wrocław European Capital of Culture 2016 program |
E424955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | city-wide cultural initiative |
C33263
|
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: city-wide cultural initiative Context triple: [Wrocław European Capital of Culture 2016 program, instanceOf, city-wide cultural initiative]
-
A.
cultural event
A cultural event is a planned gathering or activity that showcases, celebrates, or transmits the traditions, arts, values, or practices of a particular community or society.
-
B.
cultural institution program
chosen
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.
-
C.
cultural event series
A cultural event series is a recurring, thematically connected set of public programs—such as performances, exhibitions, talks, or festivals—designed to showcase, celebrate, and explore specific cultural expressions or traditions over time.
-
D.
community festival
A community festival is a locally organized public event that brings residents together to celebrate shared culture, traditions, and interests through activities, performances, and social gatherings.
-
E.
statewide initiative
A statewide initiative is a coordinated program or campaign implemented across an entire state to address a specific policy, social, economic, or public service goal.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.