Triple

T9196816
Position Surface form Disambiguated ID Type / Status
Subject Kyiv–Kovel–Poland route E220735 entity
Predicate passesThrough P225 FINISHED
Object Kovel E211354 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: Kovel | Statement: [Kyiv–Kovel–Poland route, passesThrough, Kovel]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kovel
Context triple: [Kyiv–Kovel–Poland route, passesThrough, Kovel]
  • A. Kovel chosen
    Kovel is a historic town in northwestern Ukraine, located in the Volyn region and known as a former important railway and trade hub.
  • B. Küstrin
    Küstrin is a historic town on the Oder River—now largely part of Kostrzyn nad Odrą in western Poland—that once belonged to Germany and served as a significant Prussian fortress and administrative center.
  • C. Opava
    Opava is a historic city in the Czech Republic’s Silesian region, known as a former political and cultural center of Silesia.
  • D. Valašské Meziříčí
    Valašské Meziříčí is a town in the Zlín Region of the Czech Republic known for its industrial heritage, cultural institutions, and location at the confluence of the Vsetínská and Rožnovská Bečva rivers.
  • E. Kozelets
    Kozelets is an urban-type settlement in northern Ukraine, historically known as a local administrative and trading center.
  • 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_69ca83e7ba70819088b74866d9da2c30 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccd87d6460819097234b5dd3f749b4 completed April 1, 2026, 8:34 a.m.
NED1 Entity disambiguation (via context triple) batch_69d065d8f358819085dec73f25fd5746 completed April 4, 2026, 1:14 a.m.
Created at: March 30, 2026, 7:25 p.m.