Triple
T16044184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eritrea–Ethiopia Boundary Commission ruling of 2002 |
E389173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | boundary delimitation award |
C31594
|
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: boundary delimitation award Context triple: [Eritrea–Ethiopia Boundary Commission ruling of 2002, instanceOf, boundary delimitation award]
-
A.
boundary award
chosen
A boundary award is a legal determination that formally establishes and records the precise dividing line between adjoining properties, often resolving disputes over land ownership or use.
-
B.
boundary review
A boundary review is a systematic evaluation and adjustment of geographic or organizational limits to ensure they remain fair, effective, and fit for current and future needs.
-
C.
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.
-
D.
political boundary
A political boundary is an officially recognized dividing line that separates the geographic areas of different political entities, such as countries, states, or municipalities, defining the limits of their jurisdiction and authority.
-
E.
maritime boundary decision
A maritime boundary decision is a formal determination, typically by a court, tribunal, or negotiated agreement, that defines the spatial limits and legal rights of states over adjacent or overlapping maritime zones such as territorial seas, exclusive economic zones, and continental shelves.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:56 a.m.