Triple

T4221719
Position Surface form Disambiguated ID Type / Status
Subject Przehyba E94354 entity
Predicate locatedNear P294 FINISHED
Object Stary Sącz E235600 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: Stary Sącz | Statement: [Przehyba, locatedNear, Stary Sącz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Stary Sącz
Context triple: [Przehyba, locatedNear, Stary Sącz]
  • A. Stary Sącz chosen
    Stary Sącz is a historic town in southern Poland known for its well-preserved medieval urban layout and cultural heritage.
  • B. Nowy Sącz
    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.
  • C. 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.
  • D. Haczów
    Haczów is a village in southeastern Poland known for its historic wooden architecture and cultural heritage, including one of the oldest and largest Gothic wooden churches in Europe.
  • E. Hrubieszów
    Hrubieszów is a historic town in eastern Poland near the Ukrainian border, known for its multicultural heritage and location in the Lublin region.
  • 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_69b3451997e08190851db4a9a588837d completed March 12, 2026, 10:58 p.m.
NER Named-entity recognition batch_69b34e0e06d881908e3aa8ef1a90c010 completed March 12, 2026, 11:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1132b29ac819086654ae935e819ef completed March 23, 2026, 10:17 a.m.
Created at: March 12, 2026, 11:04 p.m.