Triple

T4238868
Position Surface form Disambiguated ID Type / Status
Subject Kiev Governorate E94760 entity
Predicate hasPart P35 FINISHED
Object Chyhyryn Uyezd E430243 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: Chyhyryn Uyezd | Statement: [Kiev Governorate, hasPart, Chyhyryn Uyezd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chyhyryn Uyezd
Context triple: [Kiev Governorate, hasPart, Chyhyryn Uyezd]
  • A. Ananyiv Uyezd
    Ananyiv Uyezd was an administrative district of the Russian Empire located in the northern part of the historical Kherson region, in what is now southern Ukraine.
  • B. Zvenyhorodka Uyezd chosen
    Zvenyhorodka Uyezd was a historical administrative district centered on the town of Zvenyhorodka within the former Russian Empire’s territorial organization in what is now Ukraine.
  • C. Chernsky Uyezd
    Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
  • D. Tarashcha Uyezd
    Tarashcha Uyezd was an administrative district of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
  • E. Yefremovsky Uyezd
    Yefremovsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire centered around the town of Yefremov in what is now Tula Oblast.
  • 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_69b34537cc6481909cd0a96acbb33ef7 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e76b6e0819084d0ce137b5ba74e completed March 12, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5db80ab4481908b733572b6286b65 completed March 14, 2026, 10:04 p.m.
Created at: March 12, 2026, 11:05 p.m.