Triple
T2945905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vologda Oblast |
E79498
|
entity |
| Predicate | hasHistoricTown |
P847
|
FINISHED |
| Object | Belozersk |
E364924
|
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: Belozersk | Statement: [Vologda Oblast, hasHistoricTown, Belozersk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belozersk Context triple: [Vologda Oblast, hasHistoricTown, Belozersk]
-
A.
Belozersk
chosen
Belozersk is a historic town in northwestern Russia known for its medieval heritage and location near Lake Beloye.
-
B.
Ostashkov
Ostashkov is a historic town in western Russia situated on the shores of Lake Seliger, known as a local tourist and pilgrimage center.
-
C.
Sosnovy Bor
Sosnovy Bor is a Russian coastal town on the Gulf of Finland known for its large nuclear power plant and role as an energy and industrial center.
-
D.
Torzhok
Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
-
E.
Skovorodino
Skovorodino is a small town in Russia’s Far Eastern Amur Oblast, known historically as a railway junction on the Trans-Siberian Railway.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b3f86c819094526c2af611bfb5 |
completed | March 8, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b432e95eb48190b51692cfbd7b22a6 |
completed | March 13, 2026, 3:53 p.m. |
Created at: March 8, 2026, 2:56 p.m.