Triple

T17625681
Position Surface form Disambiguated ID Type / Status
Subject Dimitrovgrad E429833 entity
Predicate railConnection P848 FINISHED
Object Stara Zagora 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: Stara Zagora | Statement: [Dimitrovgrad, railConnection, Stara Zagora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stara Zagora
Context triple: [Dimitrovgrad, railConnection, Stara Zagora]
  • A. Stara Zagora chosen
    Stara Zagora is one of Bulgaria’s oldest cities, known for its rich history, Roman ruins, and role as an important economic and cultural center in central Bulgaria.
  • B. Blagoevgrad
    Blagoevgrad is a city in southwestern Bulgaria known as a regional cultural and educational center, home to several universities and a vibrant student population.
  • C. 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.
  • D. Shumen
    Shumen is a city in northeastern Bulgaria known for its historical significance, including nearby medieval capitals and the Monument to 1300 Years of Bulgaria.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dbc62e88190b9757dc7c52d7fee completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.