Triple
T1708830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Suslov |
E36931
|
entity |
| Predicate | placeOfBirth |
P1
|
FINISHED |
| Object |
Pavlovsky Uyezd
Pavlovsky Uyezd was an administrative district of the Russian Empire and early Russian SFSR, located within one of the empire’s central governorates.
|
E247258
|
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: Pavlovsky Uyezd | Statement: [Mikhail Suslov, placeOfBirth, Pavlovsky Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pavlovsky Uyezd Context triple: [Mikhail Suslov, placeOfBirth, Pavlovsky Uyezd]
-
A.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
B.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula Governorate.
-
C.
Venyovsky Uyezd
Venyovsky 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.
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: Pavlovsky Uyezd Triple: [Mikhail Suslov, placeOfBirth, Pavlovsky Uyezd]
Generated description
Pavlovsky Uyezd was an administrative district of the Russian Empire and early Russian SFSR, located within one of the empire’s central governorates.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pavlovsky Uyezd Target entity description: Pavlovsky Uyezd was an administrative district of the Russian Empire and early Russian SFSR, located within one of the empire’s central governorates.
-
A.
Odoyevsky Uyezd
Odoyevsky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula region.
-
B.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of the Tula Governorate.
-
C.
Venyovsky Uyezd
Venyovsky 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.
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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa63118618819085700fa84e362d60 |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6adefc088190b1c6173c4be1d5a2 |
completed | March 9, 2026, 6:38 a.m. |
| NEDg | Description generation | batch_69ae6b73bb688190bcade17d991c4862 |
completed | March 9, 2026, 6:40 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae6be4431c81909c9b4ad82226215d |
completed | March 9, 2026, 6:42 a.m. |
Created at: March 4, 2026, 7:30 p.m.