Triple

T5021416
Position Surface form Disambiguated ID Type / Status
Subject Kashubia E112858 entity
Predicate hasMajorTown P316 FINISHED
Object Kościerzyna E289205 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: Kościerzyna | Statement: [Kashubia, hasMajorTown, Kościerzyna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kościerzyna
Context triple: [Kashubia, hasMajorTown, Kościerzyna]
  • A. Kościerzyna chosen
    Kościerzyna is a historic town in northern Poland known as a local cultural and economic center within the Kashubian region.
  • B. Świnoujście
    Świnoujście is a Polish port city and seaside resort on the Baltic Sea, known for its wide beaches, spa facilities, and strategic location at the mouth of the Świna River.
  • C. Kwidzyn
    Kwidzyn is a historic town in northern Poland known for its medieval Teutonic castle complex and Gothic cathedral.
  • D. Koszalin
    Koszalin is a city in northwestern Poland near the Baltic Sea, known as a regional cultural and economic center.
  • E. Kostrzyn nad Odrą
    Kostrzyn nad Odrą is a town in western Poland near the German border, known for its strategic location at the confluence of the Oder and Warta rivers and for hosting the large Pol'and'Rock music festival.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73656edc8190b802ad38d9552b58 completed March 20, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83c2fa16c8190b03ed4d47b6090e7 completed March 28, 2026, 8:38 p.m.
Created at: March 20, 2026, 1:36 p.m.