Triple
T12755342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Novotorzhsky Uyezd |
E304844
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Torzhok |
E370640
|
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: Torzhok | Statement: [Novotorzhsky Uyezd, namedAfter, Torzhok]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Torzhok Context triple: [Novotorzhsky Uyezd, namedAfter, Torzhok]
-
A.
Torzhok
chosen
Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
-
B.
Zaraysk
Zaraysk is a historic town in Moscow Oblast, Russia, known for its well-preserved medieval kremlin and role as a former regional administrative center.
-
C.
Ivangorod
Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
-
D.
Volokolamsk
Volokolamsk is a historic town in western Russia, located northwest of Moscow and known for its medieval origins and role in regional trade and defense.
-
E.
Pervouralsk
Pervouralsk is an industrial city in Russia’s Ural region, known for its metallurgical plants and location near the geographic border between Europe and Asia.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3cf630a8819094455fc45a815b83 |
completed | May 8, 2026, 1:31 a.m. |
Created at: April 9, 2026, 5:27 p.m.