Triple

T17591600
Position Surface form Disambiguated ID Type / Status
Subject Kyustendil E428461 entity
Predicate historicalName P65 FINISHED
Object Velbazhd 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: Velbazhd | Statement: [Kyustendil, historicalName, Velbazhd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Velbazhd
Context triple: [Kyustendil, historicalName, Velbazhd]
  • A. Velbazhd chosen
    Velbazhd is the historical name of the Bulgarian town of Kyustendil, known as the site of a major medieval battle between Serbian and Bulgarian forces.
  • B. Vratsa
    Vratsa is a city in northwestern Bulgaria known as an industrial and cultural center near the Balkan Mountains.
  • C. 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.
  • D. Butovo
    Butovo is a residential district in the southern part of Moscow, Russia, known for its large housing estates and rapid post-Soviet urban development.
  • E. Targovishte
    Targovishte is a town in northeastern Bulgaria known as an administrative and economic center with historical roots dating back to the Ottoman period.
  • 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_69d889e1030481909950e140c63255b9 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e469e79dac8190953a1ce8fc015b20 completed April 19, 2026, 5:36 a.m.
Created at: April 10, 2026, 5:51 a.m.