Triple

T3361521
Position Surface form Disambiguated ID Type / Status
Subject Southern Poland E70731 entity
Predicate hasMajorCity P316 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: [Southern Poland, hasMajorCity, Nowy Sącz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nowy Sącz
Context triple: [Southern Poland, hasMajorCity, 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. Stary Sącz
    Stary Sącz is a historic town in southern Poland known for its well-preserved medieval urban layout and cultural heritage.
  • 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. Wyszogród
    Wyszogród is a historic town in central Poland on the Vistula River, known for its medieval roots and strategic location that has seen numerous military events over the centuries.
  • E. Sandomierz
    Sandomierz is a historic town in southeastern Poland, known for its well-preserved Old Town, medieval architecture, and picturesque location on the Vistula River.
  • 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_69ad85a660c48190998489309a3b4869 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb26906948190851a7b7d543a4d64 completed March 8, 2026, 5:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69b636ee2ed88190b37c7f6027d7623b completed March 15, 2026, 4:34 a.m.
Created at: March 8, 2026, 3:13 p.m.