Triple

T19364977
Position Surface form Disambiguated ID Type / Status
Subject Southern Bulgaria E484377 entity
Predicate hasMajorCity P316 FINISHED
Object Dupnitsa 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: Dupnitsa | Statement: [Southern Bulgaria, hasMajorCity, Dupnitsa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dupnitsa
Context triple: [Southern Bulgaria, hasMajorCity, Dupnitsa]
  • A. Dupnitsa chosen
    Dupnitsa is a town in southwestern Bulgaria known as a regional center near the Osogovo Mountains, with historical roots and access to mountain tourism and outdoor activities.
  • B. Berestovitsa
    Berestovitsa is a Belarusian town known for its strategic location near the border with Poland, serving as an important regional transport and customs point.
  • C. Krolevets
    Krolevets is a small historic city in northeastern Ukraine known for its traditional weaving crafts and location within Sumy Oblast.
  • D. Lyaskovets
    Lyaskovets is a small town in north-central Bulgaria known for its historical monasteries and traditional Bulgarian architecture.
  • E. Karmanovo
    Karmanovo is a rural village located within the Gagarinsky District of Smolensk Oblast in western Russia.
  • 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619aa9ff48190b1ede47fb88a682e completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:35 p.m.