Triple

T9318945
Position Surface form Disambiguated ID Type / Status
Subject Korsze E224195 entity
Predicate isSeatOf P62 FINISHED
Object Gmina Korsze E791839 NE FINISHED

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 Korsze | Statement: [Korsze, isSeatOf, Gmina Korsze]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Korsze
Context triple: [Korsze, isSeatOf, Gmina Korsze]
  • A. Gmina Korsze chosen
    Gmina Korsze is an administrative district (gmina) in northern Poland that encompasses the town of Korsze and surrounding villages.
  • B. Gmina Korzenna
    Gmina Korzenna is a rural administrative district in southern Poland, located in the Lesser Poland Voivodeship.
  • C. Gmina Czorsztyn
    Gmina Czorsztyn is a rural administrative district in southern Poland, known for its picturesque location near the Pieniny Mountains and the Czorsztyn Lake, as well as its historical castles and tourism.
  • D. Gmina Końskie
    Gmina Końskie is an administrative district in south-central Poland that includes the town of Końskie and surrounding rural areas within Końskie County.
  • E. Gmina Kościelisko
    Gmina Kościelisko is a rural administrative district in southern Poland, situated in the Tatra Mountains near Zakopane and known for its scenic landscapes and traditional highlander culture.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca8426d48481909596360f7791c7dd completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd358c7d348190a10fd8670d7756f5 completed April 1, 2026, 3:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69d0e3aa178881909e773e11c3892381 completed April 4, 2026, 10:10 a.m.
Created at: March 30, 2026, 7:38 p.m.