Triple

T1087823
Position Surface form Disambiguated ID Type / Status
Subject Zakopane E24091 entity
Predicate governingBody P46 FINISHED
Object Gmina Zakopane E24091 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 Zakopane | Statement: [Zakopane, governingBody, Gmina Zakopane]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Zakopane
Context triple: [Zakopane, governingBody, Gmina Zakopane]
  • A. Skarżysko-Kamienna
    Skarżysko-Kamienna is a town in south-central Poland known for its industrial heritage and location in the Świętokrzyskie Voivodeship.
  • B. Zakopane chosen
    Zakopane is a popular resort town in southern Poland, known as the country's "winter capital" and a gateway to the Tatra Mountains.
  • C. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • D. Ojców
    Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
  • E. Nowotarskie Podhale
    Nowotarskie Podhale is a subregion of the Podhale area in southern Poland, centered around the town of Nowy Targ and known for its highland culture and Tatra mountain landscapes.
  • 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_69a49404428c819092dcc9632f5f7b8b completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b97c64a88190bf1119fdd4940bf3 completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac42b41618819087884c292db4ed55 completed March 7, 2026, 3:22 p.m.
Created at: March 1, 2026, 7:42 p.m.