Triple

T9767509
Position Surface form Disambiguated ID Type / Status
Subject Ternopil Oblast E237032 entity
Predicate contains P35 FINISHED
Object Zboriv E716589 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: Zboriv | Statement: [Ternopil Oblast, contains, Zboriv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zboriv
Context triple: [Ternopil Oblast, contains, Zboriv]
  • A. Zboriv chosen
    Zboriv is a town in western Ukraine historically notable as the site of the 1649 Treaty of Zboriv between the Polish–Lithuanian Commonwealth and Cossack forces.
  • B. Borshchiv
    Borshchiv is a small town in western Ukraine known for its traditional embroidered clothing and historical churches.
  • C. Kremenets
    Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
  • D. Zenkiv
    Zenkiv is a historic town in central Ukraine, known for its role as a local administrative and cultural center in the Poltava region.
  • E. Semenivka
    Semenivka is a small town in northern Ukraine known for its rural character and location within the historic Chernihiv region.
  • 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_69ca84d831b8819090322686b47887ce completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cda0a2da648190836916a45d2998d7 completed April 1, 2026, 10:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1c412f0a48190b59d030b703a0e45 completed April 5, 2026, 2:08 a.m.
Created at: March 30, 2026, 8:25 p.m.