Triple
T36516162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio Amersfoort |
E900043
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | inter‑municipal cooperation |
C13569
|
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: inter‑municipal cooperation Context triple: [Regio Amersfoort, instanceOf, inter‑municipal cooperation]
-
A.
inter-district collaborative
An inter-district collaborative is a structured partnership among multiple school districts that share resources, expertise, and decision-making to improve educational services and outcomes across their combined communities.
-
B.
international municipal partnership
An international municipal partnership is a formal, collaborative relationship between local governments in different countries to share knowledge, resources, and best practices for mutual development and problem-solving.
-
C.
territorial cooperation programme
A territorial cooperation programme is a coordinated framework of policies, projects, and funding mechanisms designed to foster collaboration across regions or borders to address shared challenges and promote balanced territorial development.
-
D.
intergovernmental partnership
An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
-
E.
collective municipality
chosen
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.