Triple

T11161900
Position Surface form Disambiguated ID Type / Status
Subject Yantra River E264055 entity
Predicate nearbySettlement P350 FINISHED
Object Svishtov E848683 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: Svishtov | Statement: [Yantra River, nearbySettlement, Svishtov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svishtov
Context triple: [Yantra River, nearbySettlement, Svishtov]
  • A. Svishtov chosen
    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.
  • B. Sliven
    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.
  • 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. Pazardzhik
    Pazardzhik is a city in southern Bulgaria known as a regional economic and cultural center in the Upper Thracian Plain.
  • E. 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.
  • 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_69d6aa9ccddc8190868998c8b7beb060 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8832fe88190a74d81f9ed547baa completed April 9, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69e496d1ffa48190b29b4d4b71803564 completed April 19, 2026, 8:48 a.m.
Created at: April 8, 2026, 9:29 p.m.