Triple
T38289941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian–Russian Pomor trade region |
E1022329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border maritime trading area |
C7343
|
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: cross-border maritime trading area Context triple: [Norwegian–Russian Pomor trade region, instanceOf, cross-border maritime trading area]
-
A.
cross-border area
chosen
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
B.
maritime border
A maritime border is a legally defined boundary at sea that separates the territorial waters, exclusive economic zones, or other maritime jurisdictions of neighboring states.
-
C.
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.
-
D.
regional maritime agreement
A regional maritime agreement is a formal arrangement among neighboring states that governs the use, management, and protection of shared seas and ocean spaces within a specific geographic area.
-
E.
maritime trade exchange
A maritime trade exchange is a structured marketplace or platform where participants buy, sell, and negotiate shipping services, cargo space, and related maritime trade instruments under defined rules and standards.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.