Triple

T791355
Position Surface form Disambiguated ID Type / Status
Subject Beskid Sądecki E16920 entity
Predicate locatedNear P294 FINISHED
Object Nowy Sącz E23790 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: Nowy Sącz | Statement: [Beskid Sądecki, locatedNear, Nowy Sącz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nowy Sącz
Context triple: [Beskid Sądecki, locatedNear, Nowy Sącz]
  • A. Nowy Sącz chosen
    Nowy Sącz is a historic city in southern Poland known for its well-preserved Old Town, cultural heritage, and role as a local economic and administrative center.
  • B. 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.
  • C. Wadowice
    Wadowice is a historic town in southern Poland best known as the birthplace of Pope John Paul II.
  • D. Glogów
    Glogów is a historic town in western Poland on the Oder River, known for its medieval origins and reconstructed Old Town.
  • E. Chrzanów
    Chrzanów is a town in southern Poland known for its historical architecture and role as a local industrial and administrative center.
  • 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_69a4936cb7448190914f5fe4b8d81607 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a798c7608190b9c79c52a1fe0859 completed March 1, 2026, 8:54 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac427da0348190a8ae16db2a048d0b completed March 7, 2026, 3:21 p.m.
Created at: March 1, 2026, 7:38 p.m.