Triple

T3118230
Position Surface form Disambiguated ID Type / Status
Subject Simferopol Railway Station E65113 entity
Predicate connectsTo P845 FINISHED
Object Kharkiv E38108 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: Kharkiv | Statement: [Simferopol Railway Station, connectsTo, Kharkiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kharkiv
Context triple: [Simferopol Railway Station, connectsTo, Kharkiv]
  • A. Kharkiv chosen
    Kharkiv is Ukraine’s second-largest city and a major industrial, cultural, and educational center in the northeast of the country.
  • B. Kremenchuk
    Kremenchuk is an industrial city in central Ukraine on the Dnieper River, historically significant as a major transport and strategic hub.
  • C. Dnipro
    Dnipro is one of Ukraine’s largest industrial and cultural centers, located on the Dnieper River in the central-eastern part of the country.
  • D. Kyiv
    Kyiv is the capital and largest city of Ukraine, serving as its political, cultural, and economic center.
  • E. Chernihiv
    Chernihiv is a historic city in northern Ukraine known for its ancient churches, rich cultural heritage, and role as a regional administrative and memorial 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_69ad857fcc088190b0c4d45a5cde6f61 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada4e73cc88190846ef37ccf1a0de7 completed March 8, 2026, 4:33 p.m.
NED1 Entity disambiguation (via context triple) batch_69b432e95eb48190b51692cfbd7b22a6 completed March 13, 2026, 3:53 p.m.
Created at: March 8, 2026, 3:04 p.m.