Triple

T5951793
Position Surface form Disambiguated ID Type / Status
Subject Pazardzhik E132414 entity
Predicate hasNearbyCity P350 FINISHED
Object Plovdiv E191700 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: Plovdiv | Statement: [Pazardzhik, hasNearbyCity, Plovdiv]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Plovdiv
Context triple: [Pazardzhik, hasNearbyCity, Plovdiv]
  • A. Plovdiv chosen
    Plovdiv is Bulgaria’s second-largest city and one of Europe’s oldest continuously inhabited urban centers, known for its Roman amphitheater, Old Town, and rich cultural heritage.
  • B. 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.
  • C. 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.
  • D. Pazardzhik
    Pazardzhik is a city in southern Bulgaria known as a regional economic and cultural center in the Upper Thracian Plain.
  • 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 (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_69c0086b05cc8190a8f36a96927a525c completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c03981d88c8190838998494ad50a19 completed March 22, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c13557696881909b50c8b72af6878c completed March 23, 2026, 12:43 p.m.
Created at: March 22, 2026, 4:02 p.m.