Triple
T10792584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drechtsteden urban region |
E254618
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intermunicipal 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: intermunicipal cooperation Context triple: [Drechtsteden urban region, instanceOf, intermunicipal 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.
interregional relations
Interregional relations are the political, economic, social, and cultural interactions and institutionalized connections that occur between distinct geographic regions within or across states.
-
C.
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.
-
D.
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.
-
E.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:17 p.m.