Triple
T11999973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogilev Region |
E285632
|
entity |
| Predicate | containsCity |
P294
|
FINISHED |
| Object | Bobruisk |
E295542
|
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: Bobruisk | Statement: [Mogilev Region, containsCity, Bobruisk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bobruisk Context triple: [Mogilev Region, containsCity, Bobruisk]
-
A.
Babruysk
chosen
Babruysk is a historic city in eastern Belarus known as a former major Jewish cultural center and regional industrial hub.
-
B.
Vyazma
Vyazma is a historic town in Smolensk Oblast, western Russia, known for its strategic military significance, particularly during World War II.
-
C.
Baranavichy
Baranavichy is a significant industrial and railway hub city in western Belarus.
-
D.
Nesvizh
Nesvizh is a historic town in Belarus renowned for the UNESCO-listed Nesvizh Castle, a former Radziwiłł family residence and one of the country’s most important architectural and cultural landmarks.
-
E.
Borisoglebsk
Borisoglebsk is a small Russian city known for its historical architecture and location on the Vorona River in southwestern Russia.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903c26d7881909b67a31d04882eb5 |
completed | April 10, 2026, 2:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f48ae4733c81909956cc8d6bae343a |
completed | May 1, 2026, 11:13 a.m. |
Created at: April 8, 2026, 9:46 p.m.