Triple

T8336763
Position Surface form Disambiguated ID Type / Status
Subject Tuapse E195806 entity
Predicate hasHarbor P3007 FINISHED
Object Tuapse seaport E195806 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: Tuapse seaport | Statement: [Tuapse, hasHarbor, Tuapse seaport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuapse seaport
Context triple: [Tuapse, hasHarbor, Tuapse seaport]
  • A. Yalta Sea Port
    Yalta Sea Port is a major maritime harbor and transportation hub serving the resort city of Yalta on the southern coast of the Crimean Peninsula.
  • B. Murmansk seaport
    Murmansk seaport is a major ice-free Arctic port in northwestern Russia that serves as a key hub for maritime trade, fishing, and naval operations in the Barents Sea region.
  • C. Tuapse chosen
    Tuapse is a Black Sea port town in southern Russia known as a seaside resort and industrial center within Krasnodar Krai.
  • D. Severomorsk
    Severomorsk is a closed naval town in Russia’s Murmansk Oblast that serves as the main base of the Russian (formerly Soviet) Northern Fleet on the Barents Sea.
  • E. Port of Yuzhne
    The Port of Yuzhne is one of Ukraine’s largest and deepest Black Sea seaports, serving as a major hub for bulk cargo and international maritime trade.
  • 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd3fc80819097b326119107ad4d completed March 31, 2026, 8:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd95e17300819090e405c4c60b280d completed April 1, 2026, 10:02 p.m.
Created at: March 30, 2026, 5:57 p.m.