Triple

T20537010
Position Surface form Disambiguated ID Type / Status
Subject Radomsko County E504225 entity
Predicate borderedBy P224 FINISHED
Object Kłobuck County 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: Kłobuck County | Statement: [Radomsko County, borderedBy, Kłobuck County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kłobuck County
Context triple: [Radomsko County, borderedBy, Kłobuck County]
  • A. Kłobuck County chosen
    Kłobuck County is an administrative district (powiat) in the Silesian Voivodeship of southern Poland, with the town of Kłobuck as its seat.
  • B. Wołów County
    Wołów County is an administrative district in southwestern Poland’s Lower Silesian Voivodeship, encompassing towns such as Wołów and Brzeg Dolny.
  • C. Zawichost County
    Zawichost County was a historical administrative district in the Sandomierz region of Poland, centered on the town of Zawichost.
  • D. Lipno County
    Lipno County is a historical administrative district in central Poland that existed during the interwar period within the Warsaw Voivodeship.
  • E. Opatów County
    Opatów County is an administrative district in south-central Poland known for its historic town of Opatów and its location within the Świętokrzyskie region.
  • 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_69e0b4b476648190bc6019622ae54d3c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a28f2f1081908f656d790ff182ff completed April 20, 2026, 10:02 p.m.
Created at: April 16, 2026, 11:37 a.m.