Triple

T22211739
Position Surface form Disambiguated ID Type / Status
Subject Zolotonosha Uyezd E548966 entity
Predicate capital P234 FINISHED
Object Zolotonosha 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: Zolotonosha | Statement: [Zolotonosha Uyezd, capital, Zolotonosha]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zolotonosha
Context triple: [Zolotonosha Uyezd, capital, Zolotonosha]
  • A. Zolotonosha chosen
    Zolotonosha is a historic town in central Ukraine, located in the Cherkasy region on the banks of the Zolotonoshka River.
  • B. Zhukovka
    Zhukovka is a rural locality in Moscow Oblast, Russia, situated within the Odintsovsky District and known primarily as a residential settlement near Moscow.
  • C. Oreshek
    Oreshek is the historic Russian fortress on Lake Ladoga that later gave rise to the town of Shlisselburg.
  • D. Zvenyhorodka
    Zvenyhorodka is a town in central Ukraine that serves as a local administrative and cultural center within Cherkasy Oblast.
  • E. Maloyaroslavets
    Maloyaroslavets is a historic town in western Russia known for the 1812 Battle of Maloyaroslavets during Napoleon’s invasion.
  • 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_69e11e3f7e04819089806d81d5ac431e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12b2c8b608190b0047af4ac91b023 completed April 28, 2026, 9:48 p.m.
Created at: April 16, 2026, 8:36 p.m.