Triple
T2654886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tver Governorate |
E53984
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Vyshnevolotsky Uyezd
Vyshnevolotsky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tver Governorate.
|
E296246
|
NE FINISHED |
How this triple was built (4 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: Vyshnevolotsky Uyezd | Statement: [Tver Governorate, hasPart, Vyshnevolotsky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vyshnevolotsky Uyezd Context triple: [Tver Governorate, hasPart, Vyshnevolotsky Uyezd]
-
A.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
B.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tula Governorate.
-
C.
Bolokhovsky Uyezd
Bolokhovsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Tula Governorate.
-
D.
Mtsensky Uyezd
Mtsensky Uyezd was an administrative district (uyezd) within the Russian Empire, centered around the town of Mtsensk and historically part of the Tula Governorate.
-
E.
Rzhevsky Uyezd
Rzhevsky Uyezd was an administrative subdivision centered on the town of Rzhev within the historical Tver Governorate of the Russian Empire.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Vyshnevolotsky Uyezd Triple: [Tver Governorate, hasPart, Vyshnevolotsky Uyezd]
Generated description
Vyshnevolotsky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tver Governorate.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Vyshnevolotsky Uyezd Target entity description: Vyshnevolotsky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tver Governorate.
-
A.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
B.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tula Governorate.
-
C.
Bolokhovsky Uyezd
Bolokhovsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Tula Governorate.
-
D.
Mtsensky Uyezd
Mtsensky Uyezd was an administrative district (uyezd) within the Russian Empire, centered around the town of Mtsensk and historically part of the Tula Governorate.
-
E.
Rzhevsky Uyezd
Rzhevsky Uyezd was an administrative subdivision centered on the town of Rzhev within the historical Tver Governorate of the Russian Empire.
- F. None of above. chosen
Provenance (5 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd933ec008190aef1442460c4cfbc |
completed | March 7, 2026, 7:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afc02acc048190812d7d2d8b59058a |
completed | March 10, 2026, 6:54 a.m. |
| NEDg | Description generation | batch_69afc0a3dcb4819098e922989fb8165c |
completed | March 10, 2026, 6:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afc10deaa4819082ad29756b651480 |
completed | March 10, 2026, 6:58 a.m. |
Created at: March 6, 2026, 9:53 p.m.