Triple

T20135499
Position Surface form Disambiguated ID Type / Status
Subject Puldin E491013 entity
Predicate locatedInPresentDay P40 FINISHED
Object Plovdiv, Bulgaria 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: Plovdiv, Bulgaria | Statement: [Puldin, locatedInPresentDay, Plovdiv, Bulgaria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Plovdiv, Bulgaria
Context triple: [Puldin, locatedInPresentDay, Plovdiv, Bulgaria]
  • 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. Pazardzhik, Bulgaria
    Pazardzhik is a city in southern Bulgaria known as a regional administrative and cultural center on the banks of the Maritsa River.
  • C. Varna
    Varna is a major Bulgarian city on the Black Sea coast known as an important economic, cultural, and maritime center.
  • D. Varna
    Varna is a small settlement located within the municipality of Osečina in western Serbia.
  • E. 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.
  • 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66766e46c81908721fd47066dc9f8 completed April 20, 2026, 5:50 p.m.
Created at: April 11, 2026, 11:32 p.m.