Triple

T18843725
Position Surface form Disambiguated ID Type / Status
Subject Góra County E460860 entity
Predicate borderedBy P224 FINISHED
Object Wołów 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: Wołów County | Statement: [Góra County, borderedBy, Wołów County]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wołów County
Context triple: [Góra County, borderedBy, Wołów County]
  • A. Wołów County chosen
    Wołów County is an administrative district in southwestern Poland’s Lower Silesian Voivodeship, encompassing towns such as Wołów and Brzeg Dolny.
  • B. Zawichost County
    Zawichost County was a historical administrative district in the Sandomierz region of Poland, centered on the town of Zawichost.
  • C. Żary County
    Żary County is an administrative district in western Poland’s Lubusz Voivodeship, known for its seat in the town of Żary and its proximity to the German border.
  • D. Końskie County
    Końskie County is an administrative district in south-central Poland, known for its mix of small towns, rural landscapes, and historical sites.
  • E. Chęciny County
    Chęciny County was a historical administrative district in southern Poland, centered on the town of Chęciny and existing within the former Sandomierz Voivodeship.
  • 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_69d8dcfa11e4819090ab1ef5bdcd2b2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5b8ec8c5c8190b15e6394d0018573 completed April 20, 2026, 5:26 a.m.
Created at: April 10, 2026, 11:56 a.m.