Triple
T1694133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tula Governorate |
E36616
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Mikhaylovsky Uyezd
Mikhaylovsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically situated in what is now part of central Russia.
|
E226357
|
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: Mikhaylovsky Uyezd | Statement: [Tula Governorate, hasPart, Mikhaylovsky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhaylovsky Uyezd Context triple: [Tula Governorate, hasPart, Mikhaylovsky Uyezd]
-
A.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
B.
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.
-
C.
Epifansky Uyezd
Epifansky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
D.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
E.
Chernsky Uyezd
Chernsky 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: Mikhaylovsky Uyezd Triple: [Tula Governorate, hasPart, Mikhaylovsky Uyezd]
Generated description
Mikhaylovsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically situated in what is now part of central Russia.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Mikhaylovsky Uyezd Target entity description: Mikhaylovsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically situated in what is now part of central Russia.
-
A.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
B.
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.
-
C.
Epifansky Uyezd
Epifansky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
D.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
E.
Chernsky Uyezd
Chernsky 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_69ae0aaf7a008190bf7e5808838c6c2b |
completed | March 8, 2026, 11:47 p.m. |
| NEDg | Description generation | batch_69ae0b49abfc81908876ea54c7b7dcc2 |
completed | March 8, 2026, 11:50 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae0d1bb5c881908c27bdd359e78773 |
completed | March 8, 2026, 11:58 p.m. |
Created at: March 4, 2026, 7:29 p.m.