Triple

T16592876
Position Surface form Disambiguated ID Type / Status
Subject Belgorod Oblast E403133 entity
Predicate hasCity P316 FINISHED
Object Stary Oskol E388743 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: Stary Oskol | Statement: [Belgorod Oblast, hasCity, Stary Oskol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stary Oskol
Context triple: [Belgorod Oblast, hasCity, Stary Oskol]
  • A. Stary Oskol chosen
    Stary Oskol is a city in Belgorod Oblast, Russia, known for its significant iron ore mining and metallurgical industries.
  • B. Ostrogozhsk
    Ostrogozhsk is a historic town in Voronezh Oblast, Russia, known as a regional center with roots dating back to the 17th century.
  • C. Zvenigorod
    Zvenigorod is a historic town near Moscow, Russia, known for its ancient monasteries, traditional Russian architecture, and role as a cultural and spiritual center.
  • D. 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.
  • E. Torzhok
    Torzhok is a historic town in western Russia known for its medieval architecture, traditional goldwork embroidery, and location on the Tvertsa River.
  • 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_69d88387363c8190a97a0c942130de97 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e35d6fcaa48190b1ba7dc3b792041a completed April 18, 2026, 10:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00c29465188190a2ba6e3a7b695de3 completed May 10, 2026, 5:38 p.m.
Created at: April 10, 2026, 5:16 a.m.