Triple

T5386874
Position Surface form Disambiguated ID Type / Status
Subject Bulgars E120221 entity
Predicate capitalCity P204 FINISHED
Object Pliska E125613 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: Pliska | Statement: [Bulgars, capitalCity, Pliska]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pliska
Context triple: [Bulgars, capitalCity, Pliska]
  • A. Pliska chosen
    Pliska was the first capital city of the early medieval First Bulgarian Empire, serving as its political and administrative center.
  • B. Tarnovo
    Tarnovo, often called Veliko Tarnovo, is a historic Bulgarian city famed as a medieval capital and cultural stronghold, known for its dramatic hillside setting and well-preserved architectural heritage.
  • C. Pleven
    Pleven is a major city in northern Bulgaria known for its historical significance, particularly the Siege of Pleven during the Russo-Turkish War, and its role as an economic and cultural center in the region.
  • D. Smolyan
    Smolyan is a Bulgarian town known as an administrative, cultural, and tourist center in the Rhodope Mountains.
  • 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_69bd46354c648190a38b26f107010a96 completed March 20, 2026, 1:05 p.m.
NER Named-entity recognition batch_69bd86f6f39c8190aa6af12370e3d12b completed March 20, 2026, 5:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf335b5acc81908c43776b614e9c1a completed March 22, 2026, 12:10 a.m.
Created at: March 20, 2026, 2:03 p.m.