Triple
T34931218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Russia–Ukraine agreement on the Sea of Azov and Kerch Strait |
E1007439
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | treaty on navigation |
C566
|
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: treaty on navigation Context triple: [2003 Russia–Ukraine agreement on the Sea of Azov and Kerch Strait, instanceOf, treaty on navigation]
-
A.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
B.
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.
-
C.
navigable waterway
A navigable waterway is a natural or artificial body of water, such as a river, canal, or channel, that is deep and wide enough for vessels to travel safely for transportation or commerce.
-
D.
border treaty
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.
-
E.
treaty port concession
A treaty port concession is a designated area within a host country’s port where, under unequal treaty arrangements, foreign powers exercise special commercial, legal, and administrative privileges distinct from local jurisdiction.
- 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.