Triple

T11486784
Position Surface form Disambiguated ID Type / Status
Subject Remscheid E272299 entity
Predicate hasTwinTown P919 FINISHED
Object Dobrich E269156 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: Dobrich | Statement: [Remscheid, hasTwinTown, Dobrich]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dobrich
Context triple: [Remscheid, hasTwinTown, Dobrich]
  • A. Dobrich chosen
    Dobrich is a city in northeastern Bulgaria that serves as the administrative and economic center of the Dobrich Province in the historical region of Southern Dobruja.
  • B. 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.
  • C. 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.
  • D. Svishtov
    Svishtov is a town in northern Bulgaria on the Danube River, known for its historical significance, including proximity to the ancient Roman military site of Novae.
  • E. Burgas
    Burgas is a major Bulgarian city and industrial center on the Black Sea coast, known for its large seaport and role as a key maritime and logistics hub in the 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85a1fc9688190aacc2eed64229b79 completed April 10, 2026, 2:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69e624b12c04819085cc5f7dd64283ca completed April 20, 2026, 1:05 p.m.
Created at: April 8, 2026, 9:36 p.m.