Triple

T20368530
Position Surface form Disambiguated ID Type / Status
Subject Bulgarian rail network E496982 entity
Predicate connects P390 FINISHED
Object Vidin 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: Vidin | Statement: [Bulgarian rail network, connects, Vidin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vidin
Context triple: [Bulgarian rail network, connects, Vidin]
  • A. Vidin chosen
    Vidin is a historic city and river port in northwestern Bulgaria on the Danube, known for its medieval fortress and role as a regional center during the Second Bulgarian Empire.
  • B. Velbazhd
    Velbazhd is the historical name of the Bulgarian town of Kyustendil, known as the site of a major medieval battle between Serbian and Bulgarian forces.
  • C. Pleven
    Pleven is a major city in northern Bulgaria known for its historical significance, particularly the Siege of Pleven during the Russo-Turkish War, and its role as an economic and cultural center in the region.
  • D. Yambol
    Yambol is a city in southeastern Bulgaria known for its location on the Tundzha River and its historical and cultural significance in the region.
  • E. Razgrad
    Razgrad is a city in northeastern Bulgaria known as an administrative, economic, and cultural center of the region.
  • 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_69e0b4a4f9b081908a5a021919c21ccb completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e678734b188190bb2c5863023f9f8c completed April 20, 2026, 7:03 p.m.
Created at: April 16, 2026, 11:26 a.m.