Triple
T11178403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishnevo |
E264471
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Vishnevo, Belarus |
E264471
|
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: Vishnevo, Belarus | Statement: [Vishnevo, hasAlternativeName, Vishnevo, Belarus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vishnevo, Belarus Context triple: [Vishnevo, hasAlternativeName, Vishnevo, Belarus]
-
A.
Babruysk
Babruysk is a historic city in eastern Belarus known as a former major Jewish cultural center and regional industrial hub.
-
B.
Novopolotsk
Novopolotsk is an industrial city in northern Belarus known for its major oil refinery and petrochemical complex.
-
C.
Vishnevo
chosen
Vishnevo is a village historically located in the former Second Polish Republic, known today as Wiszniew and situated in present-day Belarus.
-
D.
Novogrudok
Novogrudok is a historic town in western Belarus known as one of the early political centers of the Grand Duchy of Lithuania.
-
E.
Brest (Belarus)
Brest is a city in southwestern Belarus near the Polish border, known as a major transport hub and for the historic Brest Fortress, a key World War II memorial.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e899c6288190b39e090fa9cdc883 |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4839eeaac8190826007ca126ed491 |
completed | April 19, 2026, 7:26 a.m. |
Created at: April 8, 2026, 9:29 p.m.