Triple
T17416877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radomysl Uyezd |
E423511
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Zvenigorodka 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: Zvenigorodka Uyezd | Statement: [Radomysl Uyezd, borderedBy, Zvenigorodka Uyezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zvenigorodka Uyezd Context triple: [Radomysl Uyezd, borderedBy, Zvenigorodka Uyezd]
-
A.
Vyazemsky Uyezd
Vyazemsky Uyezd was a historical administrative district of the Smolensk Governorate in the Russian Empire.
-
B.
Zvenyhorodka Uyezd
chosen
Zvenyhorodka Uyezd was a historical administrative district centered on the town of Zvenyhorodka within the former Russian Empire’s territorial organization in what is now Ukraine.
-
C.
Staritsky Uyezd
Staritsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire centered around the town of Staritsa in what is now Tver Oblast.
-
D.
Epifansky Uyezd
Epifansky 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.
- 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.