Triple

T17612517
Position Surface form Disambiguated ID Type / Status
Subject Cisna E428996 entity
Predicate isSeatOf P62 FINISHED
Object Gmina Cisna 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: Gmina Cisna | Statement: [Cisna, isSeatOf, Gmina Cisna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Cisna
Context triple: [Cisna, isSeatOf, Gmina Cisna]
  • A. Gmina Cisna chosen
    Gmina Cisna is a rural administrative district in southeastern Poland, known for its mountainous landscapes in the Bieszczady region and low population density.
  • B. Gmina Ciechocinek
    Gmina Ciechocinek is an urban-rural administrative district in north-central Poland that includes the spa town of Ciechocinek and its surrounding areas.
  • C. Gmina Wiśniowa
    Gmina Wiśniowa is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • D. Gmina Krasocin
    Gmina Krasocin is a rural administrative district in south-central Poland, located in the Świętokrzyskie Voivodeship.
  • E. Gmina Chęciny
    Gmina Chęciny is an administrative district in south-central Poland, centered on the historic town of Chęciny and known for its medieval castle and surrounding natural landscapes.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46d2eaa348190a8226eef8c0d6e31 completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 5:51 a.m.