Triple
T5747364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poltava Governorate |
E126766
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object |
Pyriatyn Uyezd
Pyriatyn Uyezd was an administrative district of the Russian Empire located within the historical Poltava region in what is now central Ukraine.
|
E562806
|
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: Pyriatyn Uyezd | Statement: [Poltava Governorate, contains, Pyriatyn Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyriatyn Uyezd Context triple: [Poltava Governorate, contains, Pyriatyn Uyezd]
-
A.
Lypovets Uyezd
Lypovets Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
-
B.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
C.
Ovruch Uyezd
Ovruch Uyezd was an administrative district centered on the town of Ovruch within the historical Russian Empire’s provincial system in what is now northern Ukraine.
-
D.
Kimrsky Uyezd
Kimrsky Uyezd was an administrative district (uyezd) within the former Tver Governorate of the Russian Empire.
-
E.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of 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: Pyriatyn Uyezd Triple: [Poltava Governorate, contains, Pyriatyn Uyezd]
Generated description
Pyriatyn Uyezd was an administrative district of the Russian Empire located within the historical Poltava region in what is now central Ukraine.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Pyriatyn Uyezd Target entity description: Pyriatyn Uyezd was an administrative district of the Russian Empire located within the historical Poltava region in what is now central Ukraine.
-
A.
Lypovets Uyezd
Lypovets Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
-
B.
Chernsky Uyezd
Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
-
C.
Ovruch Uyezd
Ovruch Uyezd was an administrative district centered on the town of Ovruch within the historical Russian Empire’s provincial system in what is now northern Ukraine.
-
D.
Kimrsky Uyezd
Kimrsky Uyezd was an administrative district (uyezd) within the former Tver Governorate of the Russian Empire.
-
E.
Zaraysky Uyezd
Zaraysky Uyezd was an administrative district (uyezd) within the Russian Empire, historically part of 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02885b0288190835809681a364b1f |
completed | March 22, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c107d46ebc81908ec415782611ebef |
completed | March 23, 2026, 9:28 a.m. |
| NEDg | Description generation | batch_69c1090a7bac8190b5b9e003659b4b34 |
completed | March 23, 2026, 9:34 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c10d5102348190a9ec7421b1410a99 |
completed | March 23, 2026, 9:52 a.m. |
Created at: March 22, 2026, 3:48 p.m.