Triple
T15031998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bug |
E378375
|
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: [Bug, flowsNear, Terespol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Terespol Context triple: [Bug, flowsNear, Terespol]
-
A.
Volochysk
Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
-
B.
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.
-
C.
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.
-
D.
Slutsk
Slutsk is a historic town in central Belarus known for its role as a regional center and for its traditional Slutsk belts.
-
E.
Stryj
Stryj is a historic city in western Ukraine, located on the Stryi River and known as a regional transport and industrial 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e2416081908dfba48d7f7b4a84 |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7db6f0081909ab35435c1e4ad13 |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 2:59 a.m.