Triple
T2654882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tver Governorate |
E53984
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Rzhevsky Uyezd
Rzhevsky Uyezd was an administrative subdivision centered on the town of Rzhev within the historical Tver Governorate of the Russian Empire.
|
E287822
|
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: Rzhevsky Uyezd | Statement: [Tver Governorate, hasPart, Rzhevsky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rzhevsky Uyezd Context triple: [Tver Governorate, hasPart, Rzhevsky Uyezd]
-
A.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula Governorate.
-
B.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
C.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
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.
Ryazhsky Uyezd
Ryazhsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula Governorate.
- 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: Rzhevsky Uyezd Triple: [Tver Governorate, hasPart, Rzhevsky Uyezd]
Generated description
Rzhevsky Uyezd was an administrative subdivision centered on the town of Rzhev within the historical Tver Governorate of the Russian Empire.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rzhevsky Uyezd Target entity description: Rzhevsky Uyezd was an administrative subdivision centered on the town of Rzhev within the historical Tver Governorate of the Russian Empire.
-
A.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula Governorate.
-
B.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
C.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
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.
Ryazhsky Uyezd
Ryazhsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula Governorate.
- 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_69afa054d4d0819095084088fd54a63a |
completed | March 10, 2026, 4:38 a.m. |
| NEDg | Description generation | batch_69afa0e62fa08190bf278abfce54708d |
completed | March 10, 2026, 4:41 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69afa1c8a7708190bdaefee27d596e49 |
completed | March 10, 2026, 4:44 a.m. |
Created at: March 6, 2026, 9:53 p.m.