Triple
T6299632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada–United States Great Lakes Executive Committee |
E141219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | binational governance body |
C15820
|
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: binational governance body Context triple: [Canada–United States Great Lakes Executive Committee, instanceOf, binational governance body]
-
A.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
B.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
C.
bilateral commission
chosen
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.
supranational diplomatic office
A supranational diplomatic office is an institutional body that manages and coordinates diplomatic relations, negotiations, and policy implementation on behalf of a group of sovereign states within a higher-level international or regional organization.
-
E.
supranational entity
A supranational entity is an organization or institution formed by multiple sovereign states that delegates certain decision-making powers above the national level to pursue common policies or 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_69c008cf0ad4819095def81e2bd42f9f |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:27 p.m.