Triple

T22290340
Position Surface form Disambiguated ID Type / Status
Subject Gmina Rytro E550976 entity
Predicate borderedBy P224 FINISHED
Object Gmina Stary Sącz 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 Stary Sącz | Statement: [Gmina Rytro, borderedBy, Gmina Stary Sącz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gmina Stary Sącz
Context triple: [Gmina Rytro, borderedBy, Gmina Stary Sącz]
  • A. Gmina Stary Sącz chosen
    Gmina Stary Sącz is an administrative district in southern Poland centered on the historic town of Stary Sącz in the Lesser Poland Voivodeship.
  • B. Gmina Nowy Sącz
    Gmina Nowy Sącz is an urban administrative district in southern Poland that encompasses the city of Nowy Sącz and manages its local government affairs.
  • C. Gmina Włoszczowa
    Gmina Włoszczowa is an administrative district in south-central Poland that includes the town of Włoszczowa and surrounding rural areas.
  • D. Gmina Stary Zamość
    Gmina Stary Zamość is a rural administrative district in eastern Poland, located within the Lublin Voivodeship.
  • E. Gmina Gorlice
    Gmina Gorlice is an administrative district in southern Poland that encompasses the town of Gorlice and surrounding rural areas.
  • 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_69e11e45fb848190a1b2ae21296e3a5f completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560adde88190961d8fc24c1c4b3c completed April 29, 2026, 12:51 a.m.
Created at: April 16, 2026, 8:41 p.m.