Triple

T4891146
Position Surface form Disambiguated ID Type / Status
Subject Tula Oblast E109563 entity
Predicate hasCity P316 FINISHED
Object Novomoskovsk E487615 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: Novomoskovsk | Statement: [Tula Oblast, hasCity, Novomoskovsk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Novomoskovsk
Context triple: [Tula Oblast, hasCity, Novomoskovsk]
  • A. Novomoskovsk
    Novomoskovsk is a town in central Ukraine, historically part of the Yekaterinoslav region, known for its industrial activity and location along the Samara River.
  • B. Novomoskovsk chosen
    Novomoskovsk is a significant industrial city in Russia known for its chemical industry and role as a major urban center in Tula Oblast.
  • C. Pereiaslavl
    Pereiaslavl was one of the principal urban centers of Kyivan Rus, serving as an important political, military, and cultural hub in medieval Eastern Europe.
  • D. Ivangorod
    Ivangorod is a Russian border town on the Narva River, known for its medieval fortress facing the Estonian city of Narva.
  • E. Chapaevsk
    Chapaevsk is an industrial city in southwestern Russia known for its chemical industry and location within Samara Oblast along the Volga River region.
  • 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_69bd440f71348190b99938e59fb7f9a1 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd6e07ca10819083f80f12374544b1 completed March 20, 2026, 3:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69bea467648c81909ca14744aeeee719 completed March 21, 2026, 2 p.m.
Created at: March 20, 2026, 1:28 p.m.