Triple

T35220171
Position Surface form Disambiguated ID Type / Status
Subject Kodori River E1016928 entity
Predicate hasStrategicPassage P39800 FINISHED
Object Kodori Gorge NE NERFINISHED

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: Kodori Gorge | Statement: [Kodori River, hasStrategicPassage, Kodori Gorge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStrategicPassage
Context triple: [Kodori River, hasStrategicPassage, Kodori Gorge]
  • A. hasStrategicPass chosen
    Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
  • B. hasStrategicStrait
    Indicates that one entity possesses or controls a strategically important narrow waterway that is relevant to another entity.
  • C. hasStrategicPort
    Indicates that an entity possesses or controls a port that is important for strategic, military, or economic purposes.
  • D. isStrategicCorridor
    Indicates that a route, passage, or area serves as a critical pathway for movement, access, or control, giving it significant strategic importance.
  • E. isStrategicRouteFor
    Indicates a route that is important or advantageous for achieving strategic objectives, such as military, economic, or logistical goals, for a given entity.
  • 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_69f76de072908190ab65038a8a7b6a79 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ffdd05d1908190957deb11392f4595 completed May 10, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69ffdc0d33c881908b3483bee8a96540 completed May 10, 2026, 1:14 a.m.
Created at: May 3, 2026, 4:02 p.m.