Triple
T2959528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erivan uezd |
E80011
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Surmalu uezd |
E78304
|
NE FINISHED |
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: Surmalu uezd | Statement: [Erivan uezd, borderedBy, Surmalu uezd]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Surmalu uezd Context triple: [Erivan uezd, borderedBy, Surmalu uezd]
-
A.
Surmalu uezd
chosen
Surmalu uezd was a historical administrative district of the Russian Empire’s Erivan Governorate, located in the South Caucasus region.
-
B.
Elets Uyezd
Elets Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula Governorate.
-
C.
Kimrsky Uyezd
Kimrsky Uyezd was an administrative district (uyezd) within the former Tver Governorate of the Russian Empire.
-
D.
Pronsky Uyezd
Pronsky Uyezd was an administrative subdivision (uyezd) of the Russian Empire, historically located within the Tula region.
-
E.
Dankovsky Uyezd
Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992dd4248190b5f3d4f342593b8c |
completed | March 8, 2026, 3:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0fc923d888190a68075dfaa9e90b2 |
completed | March 11, 2026, 5:24 a.m. |
Created at: March 8, 2026, 2:57 p.m.