Triple
T8269144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Bug |
E193376
|
entity |
| Predicate | flowsNear |
P350
|
FINISHED |
| Object | Terespol |
E207503
|
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: Terespol | Statement: [Western Bug, flowsNear, Terespol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terespol Context triple: [Western Bug, flowsNear, Terespol]
-
A.
Włodawa
Włodawa is a town in eastern Poland near the borders with Belarus and Ukraine, known for its multicultural heritage and proximity to the former Sobibor extermination camp.
-
B.
Terespol (Poland)
chosen
Terespol is a small town in eastern Poland situated on the Bug River, known primarily as a major road and rail border crossing point between Poland and Belarus opposite the city of Brest.
-
C.
Krasnystaw
Krasnystaw is a town in eastern Poland known for its agricultural surroundings and annual Chmielaki beer and hops festival.
-
D.
Tarnopol
Tarnopol is a historic city in western Ukraine, now known as Ternopil, which has long served as a regional cultural and administrative center.
-
E.
Orsha
Orsha is a historic city in eastern Belarus known as a regional transport hub and site of several significant battles.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb795127ac81908196008f5579f83f |
completed | March 31, 2026, 7:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd9505ecb08190bfe4025c858d7ef9 |
completed | April 1, 2026, 9:58 p.m. |
Created at: March 30, 2026, 5:50 p.m.