Triple
T31799662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jumelage with Ameland |
E811695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | town twinning partnership |
C58113
|
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: town twinning partnership Context triple: [Jumelage with Ameland, instanceOf, town twinning partnership]
-
A.
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.
-
B.
community-based partnership
A community-based partnership is a collaborative relationship between local organizations, residents, and stakeholders who share resources, decision-making, and responsibilities to address community needs and achieve mutually beneficial goals.
-
C.
bilateral commission
A bilateral commission is a formal joint body established by two parties, typically states or organizations, to negotiate, coordinate, and oversee matters of mutual interest.
-
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.
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.
- F. None of above. chosen
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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:41 p.m.