Triple

T6240426
Position Surface form Disambiguated ID Type / Status
Subject Mykolaiv E139584 entity
Predicate hasPort P35 FINISHED
Object Mykolaiv River Port E578861 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: Mykolaiv River Port | Statement: [Mykolaiv, hasPort, Mykolaiv River Port]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mykolaiv River Port
Context triple: [Mykolaiv, hasPort, Mykolaiv River Port]
  • A. Mykolaiv Sea Port chosen
    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. Kyiv River Port
    Kyiv River Port is a major inland port and transport hub on the Dnipro River serving passenger and cargo traffic for the city of Kyiv, Ukraine.
  • C. 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.
  • D. 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.
  • E. Port of Mariupol
    The Port of Mariupol is a key commercial seaport on the Sea of Azov that has historically served as a major hub for Ukraine’s maritime trade and industry.
  • 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_69c008b1c5088190ae6de2555fc05ad8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c063067d9c819085a18d9d03939266 completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69c243ff29248190abbb748601039f60 completed March 24, 2026, 7:57 a.m.
Created at: March 22, 2026, 4:23 p.m.