Triple

T22036365
Position Surface form Disambiguated ID Type / Status
Subject Khorol Uyezd E544219 entity
Predicate hasAdministrativeCenter P1474 FINISHED
Object Khorol 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: Khorol | Statement: [Khorol Uyezd, hasAdministrativeCenter, Khorol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khorol
Context triple: [Khorol Uyezd, hasAdministrativeCenter, Khorol]
  • A. Khorol chosen
    Khorol is a town in central Ukraine historically situated within the former Poltava Governorate of the Russian Empire.
  • B. Kherlen Gol
    Kherlen Gol is a major river in eastern Mongolia that flows through the steppe before joining the Amur River basin.
  • C. Selenge
    Selenge is a northern Mongolian province (aimag) known for its agricultural lands and strategic location along the border with Russia.
  • D. Khovd
    Khovd is a historically significant city in western Mongolia that serves as a regional cultural and economic center near the Altai Mountains.
  • E. Bayan-Ölgii
    Bayan-Ölgii is a western Mongolian province known for its predominantly Kazakh population, rich nomadic culture, and dramatic Altai Mountain landscapes.
  • 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127f1f95c8190a324c84313cd91ee completed April 28, 2026, 9:34 p.m.
Created at: April 16, 2026, 8:25 p.m.