Triple

T4465645
Position Surface form Disambiguated ID Type / Status
Subject Kyiv River Port E98370 entity
Predicate serves P98 FINISHED
Object city of Kyiv E17733 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: city of Kyiv | Statement: [Kyiv River Port, serves, city of Kyiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: city of Kyiv
Context triple: [Kyiv River Port, serves, city of Kyiv]
  • A. Kyiv chosen
    Kyiv is the capital and largest city of Ukraine, serving as its political, cultural, and economic center.
  • B. Kharkiv
    Kharkiv is Ukraine’s second-largest city and a major industrial, cultural, and educational center in the northeast of the country.
  • C. Kiev, Russian Empire
    Kiev, Russian Empire was a major city of the Russian Empire, now known as Kyiv, the capital of modern-day Ukraine.
  • D. Hlukhiv
    Hlukhiv is a historic city in northern Ukraine that served as an important political and cultural center of the Cossack Hetmanate in the 18th century.
  • E. Khmelnytskyi, Ukraine
    Khmelnytskyi is a regional city in western Ukraine known as an important administrative, economic, and transportation center.
  • 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_69b3454a7c608190944f5455c8031d73 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356991a588190be2f95fd957d7f99 completed March 13, 2026, 12:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69b62860151c8190b43465537b154f00 completed March 15, 2026, 3:32 a.m.
Created at: March 12, 2026, 11:34 p.m.