Triple

T22834714
Position Surface form Disambiguated ID Type / Status
Subject Gmina Kije E565911 entity
Predicate hasSettlement P1068 FINISHED
Object Lipnik 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: Lipnik | Statement: [Gmina Kije, hasSettlement, Lipnik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lipnik
Context triple: [Gmina Kije, hasSettlement, Lipnik]
  • A. Lipnik chosen
    Lipnik is a village and administrative district in south-central Poland, located within the Świętokrzyskie Voivodeship.
  • B. Lipnik
    Lipnik is a locality in present-day Poland historically known as the birthplace of renowned pianist and composer Artur Schnabel.
  • C. Lipnica Murowana
    Lipnica Murowana is a historic village in southern Poland known for its well-preserved wooden architecture and cultural heritage, including the UNESCO-listed St. Leonard Church.
  • D. Litavka
    Litavka is a river in the Czech Republic that flows through the town of Beroun before joining the Berounka River.
  • E. Lalín
    Lalín is a municipality in the interior of the province of Pontevedra, in the autonomous community of Galicia in northwestern Spain.
  • 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_69e24585ab1c81909b2b5065d15805d5 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17e2e3e7481909d12dc5008136880 completed April 29, 2026, 3:42 a.m.
Created at: April 17, 2026, 3:35 p.m.