Triple

T17683618
Position Surface form Disambiguated ID Type / Status
Subject Podrinje region E440831 entity
Predicate majorTown P316 FINISHED
Object Zvornik 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: Zvornik | Statement: [Podrinje region, majorTown, Zvornik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zvornik
Context triple: [Podrinje region, majorTown, Zvornik]
  • A. Zvornik chosen
    Zvornik is a historic town and municipality in northeastern Bosnia and Herzegovina, situated on the banks of the Drina River near the border with Serbia.
  • B. Majdanpek
    Majdanpek is a Serbian mining town known for its large copper deposits and surrounding mountainous, forested landscapes in eastern Serbia.
  • C. Konjic
    Konjic is a historic town in central Bosnia and Herzegovina known for its scenic setting on the Neretva River and its Ottoman-era stone bridge.
  • D. Jasenica
    Jasenica is a river in central Serbia that flows through the Šumadija region before joining the Velika Morava.
  • E. Bihać
    Bihać is a city in northwestern Bosnia and Herzegovina that became internationally known during the Bosnian War as a besieged enclave and designated UN "safe area."
  • 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_69d8b9e940b081908b862bb0e6e89b0d completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4704626308190bbdd98d27beb3f24 completed April 19, 2026, 6:03 a.m.
Created at: April 10, 2026, 10:02 a.m.