Triple
T35428721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal Cultural Organization of Katerini |
E1023993
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local government cultural agency |
C825
|
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: local government cultural agency Context triple: [Municipal Cultural Organization of Katerini, instanceOf, local government cultural agency]
-
A.
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.
-
B.
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.
-
C.
local governmental entity
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
municipal agency
chosen
A municipal agency is a local government organization responsible for delivering specific public services, enforcing local regulations, and managing community programs within a city or town.
-
E.
county government agency
A county government agency is a local public organization responsible for administering specific services, regulations, and programs within a county’s jurisdiction on behalf of the county government.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:03 p.m.