Triple

T18309552
Position Surface form Disambiguated ID Type / Status
Subject Ovruch Uyezd E438583 entity
Predicate namedAfter P63 FINISHED
Object Ovruch 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: Ovruch | Statement: [Ovruch Uyezd, namedAfter, Ovruch]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ovruch
Context triple: [Ovruch Uyezd, namedAfter, Ovruch]
  • A. Ovruch chosen
    Ovruch is a historic town in northern Ukraine, known for its medieval origins and cultural significance in the Polesia region.
  • B. Orlovets
    Orlovets is a prominent mountain peak in Bulgaria’s Rila Mountains, popular with hikers and climbers for its rugged alpine terrain and scenic views.
  • C. Gorokhovets
    Gorokhovets is a historic town in Vladimir Oblast, Russia, known for its well-preserved merchant architecture and scenic location amid the forests and hills of central Russia.
  • D. Khrabrovo
    Khrabrovo is a locality in Russia’s Kaliningrad region best known for hosting Khrabrovo Airport, the main air gateway to Kaliningrad.
  • E. Volnovakha
    Volnovakha is a town in eastern Ukraine that serves as an important local administrative and transport hub within Donetsk Oblast.
  • 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5021709f88190a8047dd57edc2029 completed April 19, 2026, 4:25 p.m.
Created at: April 10, 2026, 10:36 a.m.