Triple
T22921375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Commissioner (International Boundary Commission) |
E568870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | co‑chair of an international boundary commission |
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: co‑chair of an international boundary commission Context triple: [United States Commissioner (International Boundary Commission), instanceOf, co‑chair of an international boundary commission]
-
A.
boundary commission
A boundary commission is an official body established to examine, define, and recommend changes to political or administrative boundaries, often to ensure fair representation or resolve territorial disputes.
-
B.
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.
-
C.
land border
A land border is a defined line on the Earth's surface that separates the territories of two adjacent states or regions across contiguous land.
-
D.
international border
An international border is a legally defined geographic boundary that separates the territories and jurisdictions of two or more sovereign states.
-
E.
internationally recognized internal boundary
An internationally recognized internal boundary is an officially acknowledged dividing line within a sovereign state that separates its subnational units (such as states, provinces, or regions) and is accepted by the international community as part of that state's internal territorial organization.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:43 p.m.