Triple
T3677475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bug River |
E78028
|
entity |
| Predicate | passesNear |
P416
|
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: [Bug River, passesNear, Terespol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terespol Context triple: [Bug River, passesNear, 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.
Orsha
Orsha is a historic city in eastern Belarus known as a regional transport hub and site of several significant battles.
-
D.
Vishnevo
Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
-
E.
Tarnobrzeg
Tarnobrzeg is a city in southeastern Poland known historically for its sulfur mining industry and location along the Vistula River.
- 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc4643cf08190b2d10ddf4aac7407 |
completed | March 8, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b51c688e0c8190a7e9ea3fe010c361 |
completed | March 14, 2026, 8:29 a.m. |
Created at: March 8, 2026, 3:25 p.m.