Triple
T15954354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pestovo |
E386895
|
entity |
| Predicate | roadConnectionTo |
P9041
|
FINISHED |
| Object | Borovichi |
E383200
|
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: Borovichi | Statement: [Pestovo, roadConnectionTo, Borovichi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borovichi Context triple: [Pestovo, roadConnectionTo, Borovichi]
-
A.
Borovichi
chosen
Borovichi is a town in western Russia known as an industrial and transport center situated on the Msta River.
-
B.
Dubrovitsy
Dubrovitsy is a historic rural locality in Moscow Oblast, Russia, known for its ornate baroque Church of the Theotokos of the Sign and its scenic setting near the city of Podolsk.
-
C.
Borovsk
Borovsk is a historic town in western Russia known for its well-preserved architecture, monasteries, and role in regional trade and culture.
-
D.
Bolkhov
Bolkhov is a historic town in western Russia known for its old churches and traditional architecture within Oryol Oblast.
-
E.
Pleskov
Pleskov is an alternative historical or variant name for the Russian city of Pskov, a historic regional center in northwestern 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156f810148190ab4989a0e4a5f8c0 |
completed | April 16, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffbe7ab070819090232efdeecdd5fb |
completed | May 9, 2026, 11:08 p.m. |
Created at: April 10, 2026, 4:53 a.m.