Triple
T4238869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiev Governorate |
E94760
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object |
Lypovets Uyezd
Lypovets Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
|
E434536
|
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: Lypovets Uyezd | Statement: [Kiev Governorate, hasPart, Lypovets Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lypovets Uyezd Context triple: [Kiev Governorate, hasPart, Lypovets Uyezd]
-
A.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tula Governorate.
-
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.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
D.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of 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: Lypovets Uyezd Triple: [Kiev Governorate, hasPart, Lypovets Uyezd]
Generated description
Lypovets Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Lypovets Uyezd Target entity description: Lypovets Uyezd was an administrative subdivision (uyezd) of the Russian Empire located within the Kiev Governorate in what is now central Ukraine.
-
A.
Krapivensky Uyezd
Krapivensky Uyezd was an administrative district (uyezd) of the Russian Empire located within the Tula Governorate.
-
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.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
-
D.
Venyovsky Uyezd
Venyovsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5e4df07a08190be5d2a516910c491 |
completed | March 14, 2026, 10:44 p.m. |
| NEDg | Description generation | batch_69b5e56c540481909ac061c6aa620a38 |
completed | March 14, 2026, 10:47 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69b5e5c583ec8190a821f5b67e28af14 |
completed | March 14, 2026, 10:48 p.m. |
Created at: March 12, 2026, 11:05 p.m.