Triple
T31799663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jumelage with Ameland |
E811695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international municipal partnership |
C61489
|
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: international municipal partnership Context triple: [Jumelage with Ameland, instanceOf, international municipal partnership]
-
A.
international partnership organization
An international partnership organization is a collaborative entity formed by multiple countries, institutions, or stakeholders to coordinate resources, expertise, and policies toward shared global goals and initiatives.
-
B.
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.
-
C.
international public office
An international public office is an organizational unit within an intergovernmental or supranational body that performs administrative, regulatory, or policy functions across national boundaries in the public interest.
-
D.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
-
E.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
- 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.