Triple
T9882495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denmark–Sweden maritime agreements |
E180845
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maritime boundary agreement |
C18481
|
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 agreement Context triple: [Denmark–Sweden maritime agreements, instanceOf, maritime boundary agreement]
-
A.
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.
-
B.
maritime boundary delimitation case
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.
-
C.
border treaty
chosen
A border treaty is a formal agreement between two or more states that defines, clarifies, or adjusts their mutual territorial boundaries and the rules governing them.
-
D.
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.
-
E.
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.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 8:38 p.m.