Triple

T22474708
Position Surface form Disambiguated ID Type / Status
Subject Myrhorod Uyezd E555597 entity
Predicate centralSettlement P18768 FINISHED
Object Myrhorod NE NERFINISHED

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: Myrhorod | Statement: [Myrhorod Uyezd, centralSettlement, Myrhorod]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Myrhorod
Context triple: [Myrhorod Uyezd, centralSettlement, Myrhorod]
  • A. Myrhorod chosen
    Myrhorod is a historic city in central Ukraine, known for its mineral springs and as the setting of several stories by writer Nikolai Gogol.
  • B. Orikhiv
    Orikhiv is a frontline town in Ukraine’s Zaporizhzhia region that has become strategically important in the Russo-Ukrainian war.
  • C. Okhtyrka
    Okhtyrka is a historic city in northeastern Ukraine known as one of the principal centers of the Sloboda Ukraine region.
  • D. Nizhyn
    Nizhyn is a historic city in northern Ukraine known for its cultural heritage, educational institutions, and well-preserved architecture.
  • E. Khmilnyk
    Khmilnyk is a spa and resort town in central Ukraine known for its radon mineral waters and therapeutic health facilities.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e52c2048190952dc5df209b9bed completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15be2d5388190a59d11b3403d998b completed April 29, 2026, 1:16 a.m.
Created at: April 16, 2026, 8:49 p.m.