Triple

T15877711
Position Surface form Disambiguated ID Type / Status
Subject Lake Yalpuh E384992 entity
Predicate locatedNear P294 FINISHED
Object Bolhrad E874064 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: Bolhrad | Statement: [Lake Yalpuh, locatedNear, Bolhrad]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bolhrad
Context triple: [Lake Yalpuh, locatedNear, Bolhrad]
  • A. Bolhrad chosen
    Bolhrad is a town in southwestern Ukraine known as a historical center of the Bulgarian community in the Odesa region.
  • B. Partium
    Partium is a historical region of Central Europe, traditionally associated with eastern Hungary and western Romania, known for its mixed ethnic heritage and significant Reformed (Calvinist) religious presence.
  • C. Banat
    Banat is a historical region in Central Europe, now divided among Romania, Serbia, and Hungary, known for its ethnic diversity and multicultural heritage.
  • D. Bolghar
    Bolghar was the medieval capital city of Volga Bulgaria, an important political, commercial, and cultural center on the Volga River.
  • E. Bór
    Bór is the wartime nickname of Tadeusz Bór-Komorowski, the Polish general who commanded the Home Army and led the Warsaw Uprising during World War II.
  • 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_69d86da4e86481909f1325fdc971b5ec completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e155fec9d4819081efea504e1e3952 completed April 16, 2026, 9:34 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa950a890819092bc1e8895034593 completed May 9, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:51 a.m.