Triple
T9582316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Прямухино |
E231202
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Новоторжский уезд |
E304844
|
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: Новоторжский уезд | Statement: [Прямухино, historicalRegion, Новоторжский уезд]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Новоторжский уезд Context triple: [Прямухино, historicalRegion, Новоторжский уезд]
-
A.
Novotorzhsky Uyezd
chosen
Novotorzhsky Uyezd was an administrative district of the Russian Empire located within the Tver Governorate, centered around the town of Torzhok.
-
B.
Torzhoksky Uyezd
Torzhoksky Uyezd was an administrative district (uyezd) of the Russian Empire centered around the town of Torzhok within the historical Tver region.
-
C.
Novosilsky Uyezd
Novosilsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the historic Tula region.
-
D.
Vesyegonsky Uyezd
Vesyegonsky Uyezd was an administrative district (uyezd) within the former Tver Governorate of the Russian Empire.
-
E.
Korchevskoy Uyezd
Korchevskoy Uyezd was an administrative district (uyezd) of the former Tver Governorate in the Russian Empire.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99cd59008190888eb11f00f61994 |
completed | April 1, 2026, 10:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1616a11688190ba47343e4fd913fd |
completed | April 4, 2026, 7:07 p.m. |
Created at: March 30, 2026, 8:05 p.m.