Triple
T34931257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 Russia–Ukraine agreement on the Sea of Azov and Kerch Strait |
E1007439
|
entity |
| Predicate | typeOfBoundaryRegime |
P1972
|
FINISHED |
| Object | shared internal waters regime |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: shared internal waters regime | Statement: [2003 Russia–Ukraine agreement on the Sea of Azov and Kerch Strait, typeOfBoundaryRegime, shared internal waters regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBoundaryRegime Context triple: [2003 Russia–Ukraine agreement on the Sea of Azov and Kerch Strait, typeOfBoundaryRegime, shared internal waters regime]
-
A.
hasBoundaryType
chosen
Indicates that one entity has a boundary characterized by a specific type or classification in relation to another entity or context.
-
B.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for another entity.
-
D.
boundaryCurrentType
Indicates the specific kind or classification of the current that exists at or across a boundary between regions or components.
-
E.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: May 3, 2026, 4 p.m.