Triple
T1694139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tula Governorate |
E36616
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Livensky Uyezd
Livensky Uyezd was an administrative district (uyezd) within the former Tula Governorate of the Russian Empire.
|
E238416
|
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: Livensky Uyezd | Statement: [Tula Governorate, hasPart, Livensky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Livensky Uyezd Context triple: [Tula Governorate, hasPart, Livensky Uyezd]
-
A.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
B.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
C.
Epifansky Uyezd
Epifansky 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.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire 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: Livensky Uyezd Triple: [Tula Governorate, hasPart, Livensky Uyezd]
Generated description
Livensky Uyezd was an administrative district (uyezd) within the former Tula Governorate of the Russian Empire.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Livensky Uyezd Target entity description: Livensky Uyezd was an administrative district (uyezd) within the former Tula Governorate of the Russian Empire.
-
A.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
B.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
C.
Epifansky Uyezd
Epifansky 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.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire 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_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_69ae58af914c8190a27a834e3097bec7 |
completed | March 9, 2026, 5:20 a.m. |
| NEDg | Description generation | batch_69ae597198b88190b0253aa121ed35e1 |
completed | March 9, 2026, 5:24 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae59ff1234819083bbfdce270cb584 |
completed | March 9, 2026, 5:26 a.m. |
Created at: March 4, 2026, 7:29 p.m.