Triple

T11736511
Position Surface form Disambiguated ID Type / Status
Subject Kherson E279040 entity
Predicate hasPort P35 FINISHED
Object Kherson Sea Port E244367 NE 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: Kherson Sea Port | Statement: [Kherson, hasPort, Kherson Sea Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kherson Sea Port
Context triple: [Kherson, hasPort, Kherson Sea Port]
  • A. Mykolaiv Sea Port
    Mykolaiv Sea Port is a major Ukrainian maritime cargo hub on the Southern Bug River, serving as a key center for grain and industrial exports.
  • B. Port of Berdyansk
    The Port of Berdyansk is a key commercial seaport on the northern coast of the Sea of Azov, serving as an important maritime gateway for regional trade and industry.
  • C. Port of Kherson chosen
    The Port of Kherson is a key river and sea transport hub on the Dnieper River near the Black Sea, serving as an important center for cargo handling and regional trade in southern Ukraine.
  • D. Odesa harbor
    Odesa harbor is a major Black Sea port of Ukraine, serving as a key hub for maritime trade, passenger traffic, and naval activity for the city of Odesa.
  • E. Port of Chornomorsk
    The Port of Chornomorsk is a major Ukrainian Black Sea seaport and transport hub near Odesa, handling significant cargo and passenger traffic.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4edced48190b7a59dd45921828e completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f019b318188190bfb7effcf42974d2 completed April 28, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:41 p.m.