Triple
T12852429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia–Ukraine maritime disputes |
E307357
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime boundary dispute |
C25171
|
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: maritime boundary dispute Context triple: [Russia–Ukraine maritime disputes, instanceOf, maritime boundary dispute]
-
A.
maritime boundary delimitation case
chosen
A maritime boundary delimitation case is a legal dispute or proceeding in which states seek the determination or adjustment of their respective maritime zones and boundaries, such as territorial seas, exclusive economic zones, and continental shelves, in accordance with international law.
-
B.
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.
-
C.
disputed territory
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
-
D.
border conflict
A border conflict is a dispute between neighboring states or groups over the ownership, control, or demarcation of a shared territorial boundary.
-
E.
maritime zone
A maritime zone is a legally defined area of the sea, measured from a coastal state's baseline, within which specific rights, jurisdiction, and responsibilities are allocated under international law.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:36 p.m.