Triple

T8477287
Position Surface form Disambiguated ID Type / Status
Subject Primorsky Boulevard E200426 entity
Predicate hasView P854 FINISHED
Object Odesa seaport E724098 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: Odesa seaport | Statement: [Primorsky Boulevard, hasView, Odesa seaport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Odesa seaport
Context triple: [Primorsky Boulevard, hasView, Odesa seaport]
  • A. Odesa harbor chosen
    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.
  • B. 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.
  • C. 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.
  • D. 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.
  • E. Skadovsk Port
    Skadovsk Port is a Ukrainian seaport on the Black Sea that serves as a regional maritime hub for cargo and passenger transport in Kherson Oblast.
  • 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_69ca831b17988190a1f3f3413d57b820 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe51ffab881908448aff899511f2c completed March 31, 2026, 3:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce4de1fae48190a1149f639faca147 completed April 2, 2026, 11:07 a.m.
Created at: March 30, 2026, 6:12 p.m.