Triple

T8180210
Position Surface form Disambiguated ID Type / Status
Subject Chyhyryn E191040 entity
Predicate nearbyCity P350 FINISHED
Object Cherkasy E205508 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: Cherkasy | Statement: [Chyhyryn, nearbyCity, Cherkasy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cherkasy
Context triple: [Chyhyryn, nearbyCity, Cherkasy]
  • A. Cherkasy chosen
    Cherkasy is a city in central Ukraine located on the banks of the Dnieper River and serving as an important regional industrial and cultural center.
  • B. Khmelnytskyi
    Khmelnytskyi is a regional city in western Ukraine known as an important administrative, economic, and cultural center.
  • C. Lutsk
    Lutsk is a historic city in northwestern Ukraine, known as the administrative center of Volyn Oblast and one of the region’s oldest cultural and economic hubs.
  • D. Rivne
    Rivne is a city in western Ukraine that serves as an important regional administrative, economic, and cultural center.
  • E. Zhytomyr
    Zhytomyr is a historic city in northwestern Ukraine known as an important regional center and the birthplace of pioneering rocket engineer Sergei Korolev.
  • 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_69ca82c4538081909404325aa5639483 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4ac012948190bb4e2448561692e6 completed March 31, 2026, 4:17 a.m.
NED1 Entity disambiguation (via context triple) batch_69ce1cb9c9e0819080ea2875b22537ec completed April 2, 2026, 7:37 a.m.
Created at: March 30, 2026, 5:40 p.m.