Triple

T3842930
Position Surface form Disambiguated ID Type / Status
Subject Jevanshir uezd E93495 entity
Predicate borderedBy P224 FINISHED
Object Elisavetpol uezd E11206 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: Elisavetpol uezd | Statement: [Jevanshir uezd, borderedBy, Elisavetpol uezd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elisavetpol uezd
Context triple: [Jevanshir uezd, borderedBy, Elisavetpol uezd]
  • A. Elisavetpol Governorate chosen
    Elisavetpol Governorate was an administrative division of the Russian Empire in the South Caucasus, centered around the city of Ganja in what is now western Azerbaijan.
  • 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. Epifansky Uyezd
    Epifansky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
  • D. Kashirsky Uyezd
    Kashirsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
  • E. Ananyiv Uyezd
    Ananyiv Uyezd was an administrative district of the Russian Empire located in the northern part of the historical Kherson region, in what is now southern Ukraine.
  • 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_69aed96ce578819084ab16e3439976c9 completed March 9, 2026, 2:30 p.m.
NER Named-entity recognition batch_69aeebb397ac81908f74a42a0eeb8682 completed March 9, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5122ba6a4819099986e50f42f2a92 completed March 14, 2026, 7:45 a.m.
Created at: March 9, 2026, 3:18 p.m.