Triple

T8440044
Position Surface form Disambiguated ID Type / Status
Subject Chernihiv region E199327 entity
Predicate containsCity P294 FINISHED
Object Pryluky E442804 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: Pryluky | Statement: [Chernihiv region, containsCity, Pryluky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pryluky
Context triple: [Chernihiv region, containsCity, Pryluky]
  • A. Pryluky chosen
    Pryluky is a historic city in northern Ukraine known for its Cossack heritage and role as a regional cultural and economic center.
  • B. Kolodiazhne
    Kolodiazhne is a village in northwestern Ukraine known for being closely associated with the life and creative work of the renowned poet Lesya Ukrainka.
  • C. Lokhvytsia
    Lokhvytsia is a town in central Ukraine, historically part of the Poltava region and known for its role in regional trade and agriculture.
  • D. Kremenets
    Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
  • E. Vyzhnytsia
    Vyzhnytsia is a small town in western Ukraine’s Chernivtsi Oblast, historically part of Bukovina and known as the original home of the Vizhnitz Hasidic dynasty.
  • 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_69ca8314cd6c8190a6b8c2a1096e18f3 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe13708988190a534e38d8254c9bd completed March 31, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce6ceee5a48190a3858a341534f7f1 completed April 2, 2026, 1:19 p.m.
Created at: March 30, 2026, 6:08 p.m.