Triple

T19364955
Position Surface form Disambiguated ID Type / Status
Subject Southern Bulgaria E484377 entity
Predicate hasMajorCity P316 FINISHED
Object Sliven 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: Sliven | Statement: [Southern Bulgaria, hasMajorCity, Sliven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sliven
Context triple: [Southern Bulgaria, hasMajorCity, Sliven]
  • A. Sliven chosen
    Sliven is a city in eastern Bulgaria known for its textile industry, historic role in Bulgarian national revival, and location near the eastern Balkan Mountains.
  • B. 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.
  • 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. 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. Asenovgrad
    Asenovgrad is a town in southern Bulgaria known as a gateway to the Rhodope Mountains and a regional center rich in historical and religious landmarks.
  • 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.