Triple
T17416872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radomysl Uyezd |
E423511
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Kiev Uyezd |
—
|
NE NERFINISHED |
How this triple was built (2 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: Kiev Uyezd | Statement: [Radomysl Uyezd, borderedBy, Kiev Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kiev Uyezd Context triple: [Radomysl Uyezd, borderedBy, Kiev Uyezd]
-
A.
Kiev Uyezd
chosen
Kiev Uyezd was an administrative subdivision (uyezd) centered on the city of Kiev within the former Kiev Governorate of the Russian Empire.
-
B.
Poltava Uyezd
Poltava Uyezd was an administrative subdivision (uyezd) of the Russian Empire centered around the city of Poltava in what is now central Ukraine.
-
C.
Nizhyn Uyezd
Nizhyn Uyezd was an administrative district centered on the town of Nizhyn within the historical territorial divisions of the Russian Empire.
-
D.
Vinnytsia Uyezd
Vinnytsia Uyezd was a historical administrative district of the Russian Empire and later Ukraine, centered around the city of Vinnytsia.
-
E.
Myrhorod Uyezd
Myrhorod Uyezd was an administrative district (uyezd) within the Poltava Governorate of the Russian Empire and later the Ukrainian SSR, centered around the town of Myrhorod.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44232ecdc8190ac8958c1780fea19 |
completed | April 19, 2026, 2:47 a.m. |
Created at: April 10, 2026, 5:46 a.m.