Triple
T1694128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tula Governorate |
E36616
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Belevsky Uyezd
Belevsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula region.
|
E213300
|
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: Belevsky Uyezd | Statement: [Tula Governorate, hasPart, Belevsky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belevsky Uyezd Context triple: [Tula Governorate, hasPart, Belevsky Uyezd]
-
A.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within 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.
Yefremovsky Uyezd
Yefremovsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire centered around the town of Yefremov in what is now Tula Oblast.
-
E.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula 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: Belevsky Uyezd Triple: [Tula Governorate, hasPart, Belevsky Uyezd]
Generated description
Belevsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula region.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Belevsky Uyezd Target entity description: Belevsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula region.
-
A.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within 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.
Yefremovsky Uyezd
Yefremovsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire centered around the town of Yefremov in what is now Tula Oblast.
-
E.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa62b228988190a7d19003ddf10ce5 |
completed | March 6, 2026, 5:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adeac88e488190aeb6e7a1063405b7 |
completed | March 8, 2026, 9:31 p.m. |
| NEDg | Description generation | batch_69adeb8a0a64819087e4505089e93093 |
completed | March 8, 2026, 9:35 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adec6fcaac8190b43d0cd1aa613c95 |
completed | March 8, 2026, 9:38 p.m. |
Created at: March 4, 2026, 7:29 p.m.