Triple

T2877015
Position Surface form Disambiguated ID Type / Status
Subject Kerch Strait E56900 entity
Predicate hasNavigationRestriction P99 FINISHED
Object controlled access to Sea of Azov 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: controlled access to Sea of Azov | Statement: [Kerch Strait, hasNavigationRestriction, controlled access to Sea of Azov]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNavigationRestriction
Context triple: [Kerch Strait, hasNavigationRestriction, controlled access to Sea of Azov]
  • A. hasSemanticRestriction
    Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
  • B. hasNavigationAccess
    Indicates that one entity is permitted to access or use the navigation capabilities or navigation-related resources of another entity.
  • C. hasAccessRestrictionHistory
    Indicates that there exists a record or sequence of past changes detailing how access to something has been restricted over time.
  • D. hasNavigationUse
    Indicates that something is used for navigation or serves a navigational function in relation to another entity.
  • E. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe007329c8190b0bc1851c7307124 completed March 7, 2026, 8:21 a.m.
PD Predicate disambiguation batch_69abdd142e4c8190b424cb0c5ff40d04 completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 10:03 p.m.