Triple

T22720951
Position Surface form Disambiguated ID Type / Status
Subject Gmina Końskie E561856 entity
Predicate hasCentralTown P1474 FINISHED
Object Końskie 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: Końskie | Statement: [Gmina Końskie, hasCentralTown, Końskie]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Końskie
Context triple: [Gmina Końskie, hasCentralTown, Końskie]
  • A. Końskie chosen
    Końskie is a town in south-central Poland known historically as a local industrial and administrative center.
  • B. Kowary
    Kowary is a small town in southwestern Poland, located in the Lower Silesian Voivodeship near the Karkonosze Mountains, known historically for mining and tourism.
  • C. Krzemień
    Krzemień is a prominent mountain peak in Poland’s Bieszczady range, known for its scenic hiking routes and panoramic views of the surrounding Carpathian landscape.
  • D. Kobylnica
    Kobylnica is a village in northern Poland, located in the Pomeranian Voivodeship and serving as a local transport hub and administrative center for the surrounding rural area.
  • E. Ujazd
    Ujazd is a small historic town in southwestern Poland known for its medieval origins and traditional Silesian character.
  • 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17911a4fc81908a125209aea77e22 completed April 29, 2026, 3:20 a.m.
Created at: April 17, 2026, 3:19 p.m.